Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd205ef48c29a7ca603a51243a90e675ac30aadfc85f9160d6c454ceedce8ef9

Tx prefix hash: 7429ead37bbffd4b95c7754cab9b00ef2cdb5b413aa05494e0bc8931df926505
Tx public key: 37556f0d5a202941d22e79748ba7869f4eef48040044c09a8a7c4c7ca40cfede
Timestamp: 1718313142 Timestamp [UCT]: 2024-06-13 21:12:22 Age [y:d:h:m:s]: 00:224:14:15:17
Block: 1043570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160679 RingCT/type: yes/0
Extra: 0137556f0d5a202941d22e79748ba7869f4eef48040044c09a8a7c4c7ca40cfede0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8541a93c743827cb709c9fc9c93b110dcb2df6520f5e3e7887cbb07dc6ddad9c 0.600000000000 1512725 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": 1043580, "vin": [ { "gen": { "height": 1043570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8541a93c743827cb709c9fc9c93b110dcb2df6520f5e3e7887cbb07dc6ddad9c" } } ], "extra": [ 1, 55, 85, 111, 13, 90, 32, 41, 65, 210, 46, 121, 116, 139, 167, 134, 159, 78, 239, 72, 4, 0, 68, 192, 154, 138, 124, 76, 124, 164, 12, 254, 222, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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