Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69181860c5e671f3b16e7b63dd7638b4960016c37da9dc3f93855ba4d7dda916

Tx prefix hash: 4afdab942b194b097d79d513724206bcb4003a70380379cbb8a45a9bb214206d
Tx public key: 25e2f07fde088d2d967fa87775669fdf10bf9a4f0f23930ac6f2e518404e8f83
Timestamp: 1719081175 Timestamp [UCT]: 2024-06-22 18:32:55 Age [y:d:h:m:s]: 00:358:22:43:38
Block: 1049925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256458 RingCT/type: yes/0
Extra: 0125e2f07fde088d2d967fa87775669fdf10bf9a4f0f23930ac6f2e518404e8f8302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fce1dd6742d669c2eb5bb90b7fa2a987d38fc270f87dd6fccd3b2eb00320aeee 0.600000000000 1520042 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": 1049935, "vin": [ { "gen": { "height": 1049925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fce1dd6742d669c2eb5bb90b7fa2a987d38fc270f87dd6fccd3b2eb00320aeee" } } ], "extra": [ 1, 37, 226, 240, 127, 222, 8, 141, 45, 150, 127, 168, 119, 117, 102, 159, 223, 16, 191, 154, 79, 15, 35, 147, 10, 198, 242, 229, 24, 64, 78, 143, 131, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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