Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484b54815446857d66700fcb2ce1be44520ffe5d7a57a13eab1c31b2c6cd293a

Tx prefix hash: 72edaa0f87b520564b5770a040f9ae1c9050737a7aae1080835b684f0cf299ca
Tx public key: dc73df416ffbdb751e86e3b200ed7cc7edcae1cb91c68b0f25017e04d3ba282c
Timestamp: 1717837768 Timestamp [UCT]: 2024-06-08 09:09:28 Age [y:d:h:m:s]: 00:298:23:13:03
Block: 1039631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213651 RingCT/type: yes/0
Extra: 01dc73df416ffbdb751e86e3b200ed7cc7edcae1cb91c68b0f25017e04d3ba282c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d88bd67ad44f75a162ff997917c670f6dd92e58661f2cf82f02353b1493f574 0.600000000000 1508276 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": 1039641, "vin": [ { "gen": { "height": 1039631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d88bd67ad44f75a162ff997917c670f6dd92e58661f2cf82f02353b1493f574" } } ], "extra": [ 1, 220, 115, 223, 65, 111, 251, 219, 117, 30, 134, 227, 178, 0, 237, 124, 199, 237, 202, 225, 203, 145, 198, 139, 15, 37, 1, 126, 4, 211, 186, 40, 44, 2, 17, 0, 0, 0, 4, 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