Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd33e28bdce4a8ed6bb52dad2a3023e1b4501ac7fc8e7b19606604852003364d

Tx prefix hash: 53e41f921d3875d10fc8666e008e196935a440ace9a2e24ae179ff2b27b1428f
Tx public key: 745b4f0d5b73d0385cc7664c0c354ef61804fdc32fea860b16b340e5f0044283
Timestamp: 1694393361 Timestamp [UCT]: 2023-09-11 00:49:21 Age [y:d:h:m:s]: 02:062:22:14:48
Block: 845446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564662 RingCT/type: yes/0
Extra: 01745b4f0d5b73d0385cc7664c0c354ef61804fdc32fea860b16b340e5f004428302110000000133af99f4000000000000000000

1 output(s) for total of 0.969809656000 dcy

stealth address amount amount idx
00: fd8d537aa75b3863c70d26f31064eef8b5e38db3a529f832c45fc8596388f172 0.969809656000 1298834 of 0

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": 845456, "vin": [ { "gen": { "height": 845446 } } ], "vout": [ { "amount": 969809656, "target": { "key": "fd8d537aa75b3863c70d26f31064eef8b5e38db3a529f832c45fc8596388f172" } } ], "extra": [ 1, 116, 91, 79, 13, 91, 115, 208, 56, 92, 199, 102, 76, 12, 53, 78, 246, 24, 4, 253, 195, 47, 234, 134, 11, 22, 179, 64, 229, 240, 4, 66, 131, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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