Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6b0e7962390d21f890d819da37b8f074c8c61d714f5bb1ef1bff633de73be9

Tx prefix hash: 943a8a46bae150ca136466684221c7d310b33385ef0efb9eef81d99a8d992929
Tx public key: d35b0b5d397e3ad66d9bff652cb7e4e4635f40a80671ceb4ae1e8dbd415e29ea
Timestamp: 1715637445 Timestamp [UCT]: 2024-05-13 21:57:25 Age [y:d:h:m:s]: 01:003:03:06:11
Block: 1021379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263161 RingCT/type: yes/0
Extra: 01d35b0b5d397e3ad66d9bff652cb7e4e4635f40a80671ceb4ae1e8dbd415e29ea0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcb7eedf5a4170d6920a7d09f76e3493e8dc749b14551f9f24d0dc72b18230de 0.600000000000 1485684 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": 1021389, "vin": [ { "gen": { "height": 1021379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb7eedf5a4170d6920a7d09f76e3493e8dc749b14551f9f24d0dc72b18230de" } } ], "extra": [ 1, 211, 91, 11, 93, 57, 126, 58, 214, 109, 155, 255, 101, 44, 183, 228, 228, 99, 95, 64, 168, 6, 113, 206, 180, 174, 30, 141, 189, 65, 94, 41, 234, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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