Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: df6687c544d9f9b3599952f694a5d4f1018b7bbc3333a88ad721a15e912efb31

Tx prefix hash: cc5ac9cffa56bdeea823c849a066c431dbd67503e8a9182f41a589ec399e75d2
Tx public key: 6b968c59a126e1c2a4799944a3b80279fa78cb1a1999d46eb804275a6062c366
Timestamp: 1710731807 Timestamp [UCT]: 2024-03-18 03:16:47 Age [y:d:h:m:s]: 01:002:21:39:41
Block: 980738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263047 RingCT/type: yes/0
Extra: 016b968c59a126e1c2a4799944a3b80279fa78cb1a1999d46eb804275a6062c36602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849dc315ac37715309c02a062a86c690d1abe6b2d15216c2bca671772234d2d8 0.600000000000 1440819 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 980748, "vin": [ { "gen": { "height": 980738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849dc315ac37715309c02a062a86c690d1abe6b2d15216c2bca671772234d2d8" } } ], "extra": [ 1, 107, 150, 140, 89, 161, 38, 225, 194, 164, 121, 153, 68, 163, 184, 2, 121, 250, 120, 203, 26, 25, 153, 212, 110, 184, 4, 39, 90, 96, 98, 195, 102, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8