Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429d6f8cbf159270bb833d87731c082c341a07f8f2468ea22d7331ac7ce876ec

Tx prefix hash: d7054742b39559c96b7ce14a98b057510ea300d599e8fcad22cb8f6fe4c92c75
Tx public key: c5f56245e8c5e9ec349dae50c90a6448ae8c05739990af7cc498d61ac39c5033
Timestamp: 1736906827 Timestamp [UCT]: 2025-01-15 02:07:07 Age [y:d:h:m:s]: 00:058:22:38:20
Block: 1197568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41919 RingCT/type: yes/0
Extra: 01c5f56245e8c5e9ec349dae50c90a6448ae8c05739990af7cc498d61ac39c5033021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3f9f4eeb6f447ffa2f1a6be57094f26e0f303fce5e7811dfc7673a6c982651 0.600000000000 1684181 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": 1197578, "vin": [ { "gen": { "height": 1197568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3f9f4eeb6f447ffa2f1a6be57094f26e0f303fce5e7811dfc7673a6c982651" } } ], "extra": [ 1, 197, 245, 98, 69, 232, 197, 233, 236, 52, 157, 174, 80, 201, 10, 100, 72, 174, 140, 5, 115, 153, 144, 175, 124, 196, 152, 214, 26, 195, 156, 80, 51, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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