Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e363c402e5d80626c038bd3c29e0984987a89310b11abe8c6524c98eb78e1bb6

Tx prefix hash: 61a3381cb83bcae3a9d8bf6a61c274fa64b97e5150cfa7712fa38cfa77e16feb
Tx public key: e8fef98bef16af57bc7d317fcd835af5e4133a1132355d5e83d0d3ad6e268281
Timestamp: 1741327848 Timestamp [UCT]: 2025-03-07 06:10:48 Age [y:d:h:m:s]: 00:259:17:48:51
Block: 1233917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183377 RingCT/type: yes/0
Extra: 01e8fef98bef16af57bc7d317fcd835af5e4133a1132355d5e83d0d3ad6e268281021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 838ee6b51814a4c015a09ac05c3ffe24b9bcf6e6c895dd2c79ecb3f79cc015c6 0.600000000000 1720842 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": 1233927, "vin": [ { "gen": { "height": 1233917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "838ee6b51814a4c015a09ac05c3ffe24b9bcf6e6c895dd2c79ecb3f79cc015c6" } } ], "extra": [ 1, 232, 254, 249, 139, 239, 22, 175, 87, 188, 125, 49, 127, 205, 131, 90, 245, 228, 19, 58, 17, 50, 53, 93, 94, 131, 208, 211, 173, 110, 38, 130, 129, 2, 17, 0, 0, 0, 2, 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