Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c84ac22b6c5691f18d081df2a46bcf41ed7dc679728716e306279375bc8773

Tx prefix hash: 3605f30c88f844013ae930c4ef5e339a5e9e0f7527ad27f1598638d5dc277871
Tx public key: c6c996b0d843d3fd9d67ed8f4c7be76c732c2c965dc66408077f59fccb7683c0
Timestamp: 1673081521 Timestamp [UCT]: 2023-01-07 08:52:01 Age [y:d:h:m:s]: 02:142:17:40:03
Block: 669428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623753 RingCT/type: yes/0
Extra: 01c6c996b0d843d3fd9d67ed8f4c7be76c732c2c965dc66408077f59fccb7683c002110000000252542ceb000000000000000000

1 output(s) for total of 3.714557635000 dcy

stealth address amount amount idx
00: afd2d9886c19de3a446344ea7ee01727e2788acb204f1b5409ce3d30d402d13a 3.714557635000 1110745 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": 669438, "vin": [ { "gen": { "height": 669428 } } ], "vout": [ { "amount": 3714557635, "target": { "key": "afd2d9886c19de3a446344ea7ee01727e2788acb204f1b5409ce3d30d402d13a" } } ], "extra": [ 1, 198, 201, 150, 176, 216, 67, 211, 253, 157, 103, 237, 143, 76, 123, 231, 108, 115, 44, 44, 150, 93, 198, 100, 8, 7, 127, 89, 252, 203, 118, 131, 192, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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