Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bd1e05cb99b167535400090e9711178ed4bb91d2d6e22b2d613433b3736d17e

Tx prefix hash: 1047890b7260e4d52d1438330e9ec6dfc8638414fdb4cbc615f1d3c880d6a066
Tx public key: 7a7705dd58914e6a373aeab2faf89f3c50e677ae39efc5a6f364d5ab479f2f51
Timestamp: 1713921484 Timestamp [UCT]: 2024-04-24 01:18:04 Age [y:d:h:m:s]: 00:307:04:03:02
Block: 1007156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219561 RingCT/type: yes/0
Extra: 017a7705dd58914e6a373aeab2faf89f3c50e677ae39efc5a6f364d5ab479f2f510211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b1c489424aed7b96fb02a3dbd5c3406ec0d4b232b19cba4cbd40dbd19ab28e4 0.600000000000 1468406 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": 1007166, "vin": [ { "gen": { "height": 1007156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b1c489424aed7b96fb02a3dbd5c3406ec0d4b232b19cba4cbd40dbd19ab28e4" } } ], "extra": [ 1, 122, 119, 5, 221, 88, 145, 78, 106, 55, 58, 234, 178, 250, 248, 159, 60, 80, 230, 119, 174, 57, 239, 197, 166, 243, 100, 213, 171, 71, 159, 47, 81, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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