Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7cbb21dce31b76daa7ae6047d14fdab388ce0aea24c0a9f28cbc4d807263d9d

Tx prefix hash: 269c995576a4141453b44df0c0e97a682766ef82f228156c246341b0a1078e2d
Tx public key: bf84851ed946e21525173116b0856b92be54caefe504dd0afc81fbabd3d6375e
Timestamp: 1699644911 Timestamp [UCT]: 2023-11-10 19:35:11 Age [y:d:h:m:s]: 01:106:00:01:37
Block: 888805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336902 RingCT/type: yes/0
Extra: 01bf84851ed946e21525173116b0856b92be54caefe504dd0afc81fbabd3d6375e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.696658715000 dcy

stealth address amount amount idx
00: 379a4ff0e30251b6187088019d138e0cc7cea38ffaae615247ba932e2b1ac92c 0.696658715000 1344764 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": 888815, "vin": [ { "gen": { "height": 888805 } } ], "vout": [ { "amount": 696658715, "target": { "key": "379a4ff0e30251b6187088019d138e0cc7cea38ffaae615247ba932e2b1ac92c" } } ], "extra": [ 1, 191, 132, 133, 30, 217, 70, 226, 21, 37, 23, 49, 22, 176, 133, 107, 146, 190, 84, 202, 239, 229, 4, 221, 10, 252, 129, 251, 171, 211, 214, 55, 94, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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