Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60272a7c6b710031fd98c847881f2a4e58d39912384cb398e0e911c4ea8616bd

Tx prefix hash: 300f2449eee4900414338d47a5c39cb9400552d8fe8fd87daaa1f8095c7d7874
Tx public key: 77dbd86e9344d6948256fb6ac5b5bac1634251c6f0d229c85dd42ca3dbf0ce30
Timestamp: 1697317305 Timestamp [UCT]: 2023-10-14 21:01:45 Age [y:d:h:m:s]: 02:031:12:32:39
Block: 869709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542152 RingCT/type: yes/0
Extra: 0177dbd86e9344d6948256fb6ac5b5bac1634251c6f0d229c85dd42ca3dbf0ce3002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.805922123000 dcy

stealth address amount amount idx
00: ca2c88988d82ba1ff5d36cd02675a022293175ca697fcbbeff75c8a8d64d442a 0.805922123000 1324564 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": 869719, "vin": [ { "gen": { "height": 869709 } } ], "vout": [ { "amount": 805922123, "target": { "key": "ca2c88988d82ba1ff5d36cd02675a022293175ca697fcbbeff75c8a8d64d442a" } } ], "extra": [ 1, 119, 219, 216, 110, 147, 68, 214, 148, 130, 86, 251, 106, 197, 181, 186, 193, 99, 66, 81, 198, 240, 210, 41, 200, 93, 212, 44, 163, 219, 240, 206, 48, 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