Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1b3fda5556fac5fb7478c95563c80b70413d5ef236772ca14ec8c325b438e79

Tx prefix hash: 1ee2772f3f1bd2d14dafbba6164ce6dc6bcc767dc6a6814e838a41c25955dcd4
Tx public key: 8c0ce31cc2e1e953138131ab8cc70a7702cb8817f71c6fd2f66f07dda9be5cce
Timestamp: 1715563505 Timestamp [UCT]: 2024-05-13 01:25:05 Age [y:d:h:m:s]: 00:260:22:30:07
Block: 1020799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186469 RingCT/type: yes/0
Extra: 018c0ce31cc2e1e953138131ab8cc70a7702cb8817f71c6fd2f66f07dda9be5cce021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62b0637b0367b0d5f785f83682262734cbc2afc559a1c829c24d5c05c298471b 0.600000000000 1484896 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": 1020809, "vin": [ { "gen": { "height": 1020799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62b0637b0367b0d5f785f83682262734cbc2afc559a1c829c24d5c05c298471b" } } ], "extra": [ 1, 140, 12, 227, 28, 194, 225, 233, 83, 19, 129, 49, 171, 140, 199, 10, 119, 2, 203, 136, 23, 247, 28, 111, 210, 246, 111, 7, 221, 169, 190, 92, 206, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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