Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3029c43dafb995f7906418be5538e496c0b09a1c67592fd9c634118a7dcac54a

Tx prefix hash: ef7911b2779a92fe7db855cf7ec5b0d87ae9a198c1b7157504623e8bbedc56ae
Tx public key: adb3e88808d24cf4cab037f1f44a2c64af1dae327b0ad5d1f712ab4c1a6dc072
Timestamp: 1761166256 Timestamp [UCT]: 2025-10-22 20:50:56 Age [y:d:h:m:s]: 00:075:05:36:12
Block: 1395730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53862 RingCT/type: yes/0
Extra: 01adb3e88808d24cf4cab037f1f44a2c64af1dae327b0ad5d1f712ab4c1a6dc07202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bca2dfcb61072aabb1c939786a83b9992f141c92b6a0bf260b174076e8dbfb1 0.600000000000 1884013 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": 1395740, "vin": [ { "gen": { "height": 1395730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bca2dfcb61072aabb1c939786a83b9992f141c92b6a0bf260b174076e8dbfb1" } } ], "extra": [ 1, 173, 179, 232, 136, 8, 210, 76, 244, 202, 176, 55, 241, 244, 74, 44, 100, 175, 29, 174, 50, 123, 10, 213, 209, 247, 18, 171, 76, 26, 109, 192, 114, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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