Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fab02748244831dfc0eeb8590d046876aa4fa7c129356643335516d36d4b437

Tx prefix hash: bafbc1b527c00a96e3afe351c31d8f2703a42d3a30affc69cde2ba7a4652295c
Tx public key: d9545e6a940ea6e963dc53d332c147e3c3673dbb24d7a863cd13023608094f21
Timestamp: 1720673797 Timestamp [UCT]: 2024-07-11 04:56:37 Age [y:d:h:m:s]: 00:261:09:40:56
Block: 1063151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186746 RingCT/type: yes/0
Extra: 01d9545e6a940ea6e963dc53d332c147e3c3673dbb24d7a863cd13023608094f21021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d5f7a354777d6e035a9121df4e79c10500758f19c0e22549ed412074b06cab 0.600000000000 1533666 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": 1063161, "vin": [ { "gen": { "height": 1063151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d5f7a354777d6e035a9121df4e79c10500758f19c0e22549ed412074b06cab" } } ], "extra": [ 1, 217, 84, 94, 106, 148, 14, 166, 233, 99, 220, 83, 211, 50, 193, 71, 227, 195, 103, 61, 187, 36, 215, 168, 99, 205, 19, 2, 54, 8, 9, 79, 33, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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