Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e02d31989e03e7d3cffdec0ac184ba9957864118b2637a49f3aedf9c8d69750d

Tx prefix hash: 333077c81cb6417b7cd3d5a11e32afe0f0fe14adb5b242fb9ba4b3a97a87f3f3
Tx public key: b86e2f18ecc35dead3db9d0e30e547dc5440f132a8a7695cb6c5bac95037b886
Timestamp: 1722669290 Timestamp [UCT]: 2024-08-03 07:14:50 Age [y:d:h:m:s]: 00:267:11:29:19
Block: 1079684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191078 RingCT/type: yes/0
Extra: 01b86e2f18ecc35dead3db9d0e30e547dc5440f132a8a7695cb6c5bac95037b886021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b659675ce3bddd5a5e6fa131bb52cb4903cf07171320166417d65de580641496 0.600000000000 1552751 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": 1079694, "vin": [ { "gen": { "height": 1079684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b659675ce3bddd5a5e6fa131bb52cb4903cf07171320166417d65de580641496" } } ], "extra": [ 1, 184, 110, 47, 24, 236, 195, 93, 234, 211, 219, 157, 14, 48, 229, 71, 220, 84, 64, 241, 50, 168, 167, 105, 92, 182, 197, 186, 201, 80, 55, 184, 134, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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