Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: def35b3382d87d7c057e285df58656cca0a458c707b3c2d175978dc768dee592

Tx prefix hash: 9016ec7af59f9e769300102f391132d1dd1a88748101bcd62553328b78076c7d
Tx public key: bfb9087b2f1ef0793466c5bb275fec7e8598bf1211fcf03c7d61ccbf6c7a6c6d
Timestamp: 1713829023 Timestamp [UCT]: 2024-04-22 23:37:03 Age [y:d:h:m:s]: 00:308:10:25:19
Block: 1006393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220468 RingCT/type: yes/0
Extra: 01bfb9087b2f1ef0793466c5bb275fec7e8598bf1211fcf03c7d61ccbf6c7a6c6d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6abf626100d2813d4bb7c5f972ba3e5f4b6c26a64e9e548d08eb5204929b9697 0.600000000000 1467415 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": 1006403, "vin": [ { "gen": { "height": 1006393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6abf626100d2813d4bb7c5f972ba3e5f4b6c26a64e9e548d08eb5204929b9697" } } ], "extra": [ 1, 191, 185, 8, 123, 47, 30, 240, 121, 52, 102, 197, 187, 39, 95, 236, 126, 133, 152, 191, 18, 17, 252, 240, 60, 125, 97, 204, 191, 108, 122, 108, 109, 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