Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10bea391ebb90af907ee3e1ea4dc822dffec1163a09b66540e604bb73338590a

Tx prefix hash: 6a1b7d1f96d37faff9d456bdc95b52fb6844857f47f425a92e395ca5f68c900f
Tx public key: fa4d807d663a9e4dfef977eb1bf788c0cb0d631c62abc9af67aad96286c3ad69
Timestamp: 1720571346 Timestamp [UCT]: 2024-07-10 00:29:06 Age [y:d:h:m:s]: 00:141:15:21:19
Block: 1062299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101359 RingCT/type: yes/0
Extra: 01fa4d807d663a9e4dfef977eb1bf788c0cb0d631c62abc9af67aad96286c3ad6902110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f17918c5b953fc997e92a82311427718e48fc0967e82833b1a4c95172e1c0e81 0.600000000000 1532800 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": 1062309, "vin": [ { "gen": { "height": 1062299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f17918c5b953fc997e92a82311427718e48fc0967e82833b1a4c95172e1c0e81" } } ], "extra": [ 1, 250, 77, 128, 125, 102, 58, 158, 77, 254, 249, 119, 235, 27, 247, 136, 192, 203, 13, 99, 28, 98, 171, 201, 175, 103, 170, 217, 98, 134, 195, 173, 105, 2, 17, 0, 0, 0, 10, 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