Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d7d9d5b0bc9774571848e5e37e29502f879e03fc141baf1f848c8aef657f8ec

Tx prefix hash: 6423e7684e5cc11784bf5e12f3728ad9b3daf5dd264a34c25fc50f5bc2a38d90
Tx public key: 57cdb7f294eac4af436cacadb85513b238724ed58b2bab79450d5f5a23a8153a
Timestamp: 1702368852 Timestamp [UCT]: 2023-12-12 08:14:12 Age [y:d:h:m:s]: 01:108:04:53:32
Block: 911390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338459 RingCT/type: yes/0
Extra: 0157cdb7f294eac4af436cacadb85513b238724ed58b2bab79450d5f5a23a8153a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bf9f4688b5701f19d8a1d2f1d1f044a381de97b4d0c7928e41fd886de9f3de3 0.600000000000 1368592 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": 911400, "vin": [ { "gen": { "height": 911390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf9f4688b5701f19d8a1d2f1d1f044a381de97b4d0c7928e41fd886de9f3de3" } } ], "extra": [ 1, 87, 205, 183, 242, 148, 234, 196, 175, 67, 108, 172, 173, 184, 85, 19, 178, 56, 114, 78, 213, 139, 43, 171, 121, 69, 13, 95, 90, 35, 168, 21, 58, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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