Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d3f504c3484dadeafa1710e4b0bfb9dc61e8240edfc8cc5022490d99920247

Tx prefix hash: 041b5c36334040b32d462f9fc6a0a566fd5cd2fb504333a6204a63fa1b158d07
Tx public key: 697a13cdbe4e9ecf7c5de8306133fb41497c9a1f25d0bc12a8f9f51a0b8f976e
Timestamp: 1737638266 Timestamp [UCT]: 2025-01-23 13:17:46 Age [y:d:h:m:s]: 00:291:11:26:04
Block: 1203589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205857 RingCT/type: yes/0
Extra: 01697a13cdbe4e9ecf7c5de8306133fb41497c9a1f25d0bc12a8f9f51a0b8f976e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27524ade4f57b55ad5adb29a39eb006a3374968a753949eff37240fbb0d8caf1 0.600000000000 1690266 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": 1203599, "vin": [ { "gen": { "height": 1203589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27524ade4f57b55ad5adb29a39eb006a3374968a753949eff37240fbb0d8caf1" } } ], "extra": [ 1, 105, 122, 19, 205, 190, 78, 158, 207, 124, 93, 232, 48, 97, 51, 251, 65, 73, 124, 154, 31, 37, 208, 188, 18, 168, 249, 245, 26, 11, 143, 151, 110, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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