Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f7b09121213ed365af3df30d6d947fec3defd8e408806f88a7b385931f3533

Tx prefix hash: c5e02e686faa16a5cf0afdc19d2bc0a7f01cfdc67aae93a657a16c0d33fd85b2
Tx public key: 057de8332efb879e469d196dc70288f83b302373be29c620420e294393d82c63
Timestamp: 1711341624 Timestamp [UCT]: 2024-03-25 04:40:24 Age [y:d:h:m:s]: 01:049:16:13:50
Block: 985797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296482 RingCT/type: yes/0
Extra: 01057de8332efb879e469d196dc70288f83b302373be29c620420e294393d82c630211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b802d533ae5e4d434ae4726da2e4fdfbe985bcc1bf3ca30e5cadb69d8e8e525 0.600000000000 1446016 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": 985807, "vin": [ { "gen": { "height": 985797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b802d533ae5e4d434ae4726da2e4fdfbe985bcc1bf3ca30e5cadb69d8e8e525" } } ], "extra": [ 1, 5, 125, 232, 51, 46, 251, 135, 158, 70, 157, 25, 109, 199, 2, 136, 248, 59, 48, 35, 115, 190, 41, 198, 32, 66, 14, 41, 67, 147, 216, 44, 99, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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