Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bc83893cd5e3918f3fe844773abc295efb64b0158f47412a4e4a75b779e04a2

Tx prefix hash: b1b4bf776b66f6c0be06cb3118f11520e86b82c3e4b6d04453c702934ad540b6
Tx public key: 212b026fd1121205d5e2b6aa0a38cd08d6e8632c799dfcbbd465554382c9b51e
Timestamp: 1741259044 Timestamp [UCT]: 2025-03-06 11:04:04 Age [y:d:h:m:s]: 00:259:10:56:51
Block: 1233350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183168 RingCT/type: yes/0
Extra: 01212b026fd1121205d5e2b6aa0a38cd08d6e8632c799dfcbbd465554382c9b51e02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d58b9641665b054e6f20b577a0e2ec949bb00d9232b1ac4699702690128ea89 0.600000000000 1720269 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": 1233360, "vin": [ { "gen": { "height": 1233350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d58b9641665b054e6f20b577a0e2ec949bb00d9232b1ac4699702690128ea89" } } ], "extra": [ 1, 33, 43, 2, 111, 209, 18, 18, 5, 213, 226, 182, 170, 10, 56, 205, 8, 214, 232, 99, 44, 121, 157, 252, 187, 212, 101, 85, 67, 130, 201, 181, 30, 2, 17, 0, 0, 0, 12, 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