Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 359f795b6181f7112aaf9218a4d66df6edbea9ae6c847965845d3f64c82f0e58

Tx prefix hash: 9e325e48be2370d4a1598441b17a63ed3bd6e94eb75a5905c0a2bb8ba1f41ce2
Tx public key: 3ceff34b62b3fcc6d1c30f49f02276ef2723f57677e0f1d9b46ea32b4f916d5f
Timestamp: 1725191816 Timestamp [UCT]: 2024-09-01 11:56:56 Age [y:d:h:m:s]: 01:060:02:39:33
Block: 1100598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301393 RingCT/type: yes/0
Extra: 013ceff34b62b3fcc6d1c30f49f02276ef2723f57677e0f1d9b46ea32b4f916d5f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df9b518ea51f1b10b15f02e685f587592bbb43a55ce9f70efb16a1deb6be994 0.600000000000 1576577 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": 1100608, "vin": [ { "gen": { "height": 1100598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df9b518ea51f1b10b15f02e685f587592bbb43a55ce9f70efb16a1deb6be994" } } ], "extra": [ 1, 60, 239, 243, 75, 98, 179, 252, 198, 209, 195, 15, 73, 240, 34, 118, 239, 39, 35, 245, 118, 119, 224, 241, 217, 180, 110, 163, 43, 79, 145, 109, 95, 2, 17, 0, 0, 0, 5, 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