Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14d8c728162fe4ea3765bef7e421f95c44137e998dcb56f1115f5a2be2264919

Tx prefix hash: 0f356ca648e7e2c8169c9d6fd50079ee9c239c3c5b265421ca8817b13b80c995
Tx public key: 37408dd0e028d28a086444fb420f71dbc7067a6dd29130a572b42682766adbb1
Timestamp: 1694873910 Timestamp [UCT]: 2023-09-16 14:18:30 Age [y:d:h:m:s]: 01:273:13:14:50
Block: 849437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456541 RingCT/type: yes/0
Extra: 0137408dd0e028d28a086444fb420f71dbc7067a6dd29130a572b42682766adbb1021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.940724941000 dcy

stealth address amount amount idx
00: d7dfedbd5bc113e5be2229eb15b695125e0e3d3e026c7e804d9b100d188909b3 0.940724941000 1303103 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": 849447, "vin": [ { "gen": { "height": 849437 } } ], "vout": [ { "amount": 940724941, "target": { "key": "d7dfedbd5bc113e5be2229eb15b695125e0e3d3e026c7e804d9b100d188909b3" } } ], "extra": [ 1, 55, 64, 141, 208, 224, 40, 210, 138, 8, 100, 68, 251, 66, 15, 113, 219, 199, 6, 122, 109, 210, 145, 48, 165, 114, 180, 38, 130, 118, 106, 219, 177, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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