Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7681bd128a160236992dd6f6552e69e98fcd7bf99f31cdcde61861066205c25b

Tx prefix hash: 098190e7a4fd25620c7b883ce70b9ae5637049c2b15b47d6e581aebb97e6650d
Tx public key: bc2c4ed3fc20576c6f9d7cb5091cfc06a6194facf2c9a160a813cd646aac0bf4
Timestamp: 1710616474 Timestamp [UCT]: 2024-03-16 19:14:34 Age [y:d:h:m:s]: 01:029:05:21:52
Block: 979775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281856 RingCT/type: yes/0
Extra: 01bc2c4ed3fc20576c6f9d7cb5091cfc06a6194facf2c9a160a813cd646aac0bf402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b12ca3cd66aaf89484f0af5b2b09038cc83e189a389c0da04d054b19f56059 0.600000000000 1439828 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": 979785, "vin": [ { "gen": { "height": 979775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b12ca3cd66aaf89484f0af5b2b09038cc83e189a389c0da04d054b19f56059" } } ], "extra": [ 1, 188, 44, 78, 211, 252, 32, 87, 108, 111, 157, 124, 181, 9, 28, 252, 6, 166, 25, 79, 172, 242, 201, 161, 96, 168, 19, 205, 100, 106, 172, 11, 244, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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