Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512e74a0079dc3da482b4748cf9cf7a6de9a3fe374283aad20ac950f2aca4f13

Tx prefix hash: 293d8f76c5e7cbb736b30071bb0be01cc5996e7aebe02ded11db80e7bb2ac469
Tx public key: f58f93a4b8bbf869c3c5d0535878924519cc7734fdf436b7d0fa3967ccf272fa
Timestamp: 1703892486 Timestamp [UCT]: 2023-12-29 23:28:06 Age [y:d:h:m:s]: 01:031:00:55:30
Block: 924013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283273 RingCT/type: yes/0
Extra: 01f58f93a4b8bbf869c3c5d0535878924519cc7734fdf436b7d0fa3967ccf272fa02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 143f80424aab1411f1ed914c50ba00bc4a8e7fd55e9dfdc3f4fbef385eb75abc 0.600000000000 1381755 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": 924023, "vin": [ { "gen": { "height": 924013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "143f80424aab1411f1ed914c50ba00bc4a8e7fd55e9dfdc3f4fbef385eb75abc" } } ], "extra": [ 1, 245, 143, 147, 164, 184, 187, 248, 105, 195, 197, 208, 83, 88, 120, 146, 69, 25, 204, 119, 52, 253, 244, 54, 183, 208, 250, 57, 103, 204, 242, 114, 250, 2, 17, 0, 0, 0, 7, 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