Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96338824664286185651e2ae0334aa3fea3ea3b9f6601d1925e48eb0732c2a9f

Tx prefix hash: 7d2a6102d562406a87086ae351637f7a4a522c12187cc3a4842bcc817488e6fe
Tx public key: 6a85bbf1c13a5eefaa2fbeccedae7482a790ed00afb9b76500ab390055a5cbc0
Timestamp: 1699813341 Timestamp [UCT]: 2023-11-12 18:22:21 Age [y:d:h:m:s]: 01:070:13:19:37
Block: 890206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311787 RingCT/type: yes/0
Extra: 016a85bbf1c13a5eefaa2fbeccedae7482a790ed00afb9b76500ab390055a5cbc00211000000014b8f5122000000000000000000

1 output(s) for total of 0.689251909000 dcy

stealth address amount amount idx
00: a08d6376600550d00b1b6e0cf805caeafd2dbd7c52f68d2a215e0cb1902c9a1a 0.689251909000 1346227 of 0

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": 890216, "vin": [ { "gen": { "height": 890206 } } ], "vout": [ { "amount": 689251909, "target": { "key": "a08d6376600550d00b1b6e0cf805caeafd2dbd7c52f68d2a215e0cb1902c9a1a" } } ], "extra": [ 1, 106, 133, 187, 241, 193, 58, 94, 239, 170, 47, 190, 204, 237, 174, 116, 130, 167, 144, 237, 0, 175, 185, 183, 101, 0, 171, 57, 0, 85, 165, 203, 192, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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