Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e93dc5556fe500dbbe87218dceed722c963707c3e451e725d773d8b02c3768

Tx prefix hash: c9e11dd8c0e0e70f5a1bb9a722c6329e242e890ac6adf2ef0c1409acb63623fa
Tx public key: 63fef55d32dc4ff86362915bdf9b66e89073ae6bdd64fbe71cd332ebd44dcfd8
Timestamp: 1762049045 Timestamp [UCT]: 2025-11-02 02:04:05 Age [y:d:h:m:s]: 00:003:12:05:07
Block: 1403041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2494 RingCT/type: yes/0
Extra: 0163fef55d32dc4ff86362915bdf9b66e89073ae6bdd64fbe71cd332ebd44dcfd8021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c368f84077b168136c0f66a192a389eaa1c993173b09a90e6b5c6216aefe497 0.600000000000 1891368 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": 1403051, "vin": [ { "gen": { "height": 1403041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c368f84077b168136c0f66a192a389eaa1c993173b09a90e6b5c6216aefe497" } } ], "extra": [ 1, 99, 254, 245, 93, 50, 220, 79, 248, 99, 98, 145, 91, 223, 155, 102, 232, 144, 115, 174, 107, 221, 100, 251, 231, 28, 211, 50, 235, 212, 77, 207, 216, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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