Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 714f9a49403905b05ae309dce3a86e87043a693ce108e8c22a65909c6046d69e

Tx prefix hash: d1eba72534bd3d0e2cb4b126e3daf4664352019f1318a87468edd03e000c72b2
Tx public key: 3f62c5d6c262fc69ad38e36981ed95d6ac9b13ec2c9c0018eed0a3443c855fd8
Timestamp: 1718792992 Timestamp [UCT]: 2024-06-19 10:29:52 Age [y:d:h:m:s]: 00:362:08:35:09
Block: 1047561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258865 RingCT/type: yes/0
Extra: 013f62c5d6c262fc69ad38e36981ed95d6ac9b13ec2c9c0018eed0a3443c855fd802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a83fb691daab18f6d7a97e360980d14378763d6ae51eaba81e3a168e0a9c46a1 0.600000000000 1517414 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": 1047571, "vin": [ { "gen": { "height": 1047561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a83fb691daab18f6d7a97e360980d14378763d6ae51eaba81e3a168e0a9c46a1" } } ], "extra": [ 1, 63, 98, 197, 214, 194, 98, 252, 105, 173, 56, 227, 105, 129, 237, 149, 214, 172, 155, 19, 236, 44, 156, 0, 24, 238, 208, 163, 68, 60, 133, 95, 216, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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