Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bec0386cb1513f45345f27cb8e0287717d497c52af5f6c1b31b0c0768c801130

Tx prefix hash: aa5ae6ef5a3a021919c56147155c9d5fec957425eb45b2a504eee1d786e9c9ce
Tx public key: 7a74354e89c7ac80ba2486336a66cde624f8a90afedce1ca0b3dbf1f607250c6
Timestamp: 1707317505 Timestamp [UCT]: 2024-02-07 14:51:45 Age [y:d:h:m:s]: 01:120:03:43:51
Block: 952409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346969 RingCT/type: yes/0
Extra: 017a74354e89c7ac80ba2486336a66cde624f8a90afedce1ca0b3dbf1f607250c60211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c139ac2cff2f27dca65999bfe9368cad43e18d52f6c7b6afe821e05f50949d3 0.600000000000 1411385 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": 952419, "vin": [ { "gen": { "height": 952409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c139ac2cff2f27dca65999bfe9368cad43e18d52f6c7b6afe821e05f50949d3" } } ], "extra": [ 1, 122, 116, 53, 78, 137, 199, 172, 128, 186, 36, 134, 51, 106, 102, 205, 230, 36, 248, 169, 10, 254, 220, 225, 202, 11, 61, 191, 31, 96, 114, 80, 198, 2, 17, 0, 0, 0, 8, 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