Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d426541c09ce40fc341dc008e62f312608944b0f9d27c8bfde2a8eb0fa99f915

Tx prefix hash: 0f6742a9b8159ffd8d9dc7e49cdb8f62a60d6231ec688b3559fa9bb1dfe39cfd
Tx public key: 67710ae129ff2a4e010291a2803e3bc6c40c87cb7b438d9dd3332105672bac76
Timestamp: 1736628080 Timestamp [UCT]: 2025-01-11 20:41:20 Age [y:d:h:m:s]: 00:085:18:26:17
Block: 1195262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61084 RingCT/type: yes/0
Extra: 0167710ae129ff2a4e010291a2803e3bc6c40c87cb7b438d9dd3332105672bac76021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3627a451ba1fb9c079746caf8b203cf00bc9964cb25b8c72ae55ad8a35f90c3e 0.600000000000 1681851 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": 1195272, "vin": [ { "gen": { "height": 1195262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3627a451ba1fb9c079746caf8b203cf00bc9964cb25b8c72ae55ad8a35f90c3e" } } ], "extra": [ 1, 103, 113, 10, 225, 41, 255, 42, 78, 1, 2, 145, 162, 128, 62, 59, 198, 196, 12, 135, 203, 123, 67, 141, 157, 211, 51, 33, 5, 103, 43, 172, 118, 2, 17, 0, 0, 0, 1, 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