Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f51a2c77362fcbbffb6ee2548025f24aad2126d408dc492bf3006208fd3dff2

Tx prefix hash: d8fc2fecc3dd2019f33d3e587f0d7d737cca2c21a111265e952cfc3ed6dfb569
Tx public key: 3761190da4c1f3a5f733609e52bf2fd165ec4aded20dfc310e11afe4c81462c9
Timestamp: 1702820833 Timestamp [UCT]: 2023-12-17 13:47:13 Age [y:d:h:m:s]: 01:178:00:37:32
Block: 915123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388384 RingCT/type: yes/0
Extra: 013761190da4c1f3a5f733609e52bf2fd165ec4aded20dfc310e11afe4c81462c902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9ab098ae37e72346a1da73e8849d17c7a5f4fcf218e22d11f54fcbb4bcf30df 0.600000000000 1372509 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": 915133, "vin": [ { "gen": { "height": 915123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9ab098ae37e72346a1da73e8849d17c7a5f4fcf218e22d11f54fcbb4bcf30df" } } ], "extra": [ 1, 55, 97, 25, 13, 164, 193, 243, 165, 247, 51, 96, 158, 82, 191, 47, 209, 101, 236, 74, 222, 210, 13, 252, 49, 14, 17, 175, 228, 200, 20, 98, 201, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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