Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b87e43931afe407f98c1e0b40fac45049cb19430563c6ecf1c1d8869f2111e6

Tx prefix hash: ad06c831fb7fb30710e8b69ad0db3e64c1e1bc877f96ff7fb5a1bac164de6348
Tx public key: f694b69182182a78f0927d821c7a93bc1fc234ba7da9e77714751c1f7f0847ed
Timestamp: 1723659046 Timestamp [UCT]: 2024-08-14 18:10:46 Age [y:d:h:m:s]: 00:259:23:07:53
Block: 1087893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185688 RingCT/type: yes/0
Extra: 01f694b69182182a78f0927d821c7a93bc1fc234ba7da9e77714751c1f7f0847ed021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07cd74b7ee73a16521a0681f54c0ddd94de066b5eca67e33242b330ea861c798 0.600000000000 1562504 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": 1087903, "vin": [ { "gen": { "height": 1087893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07cd74b7ee73a16521a0681f54c0ddd94de066b5eca67e33242b330ea861c798" } } ], "extra": [ 1, 246, 148, 182, 145, 130, 24, 42, 120, 240, 146, 125, 130, 28, 122, 147, 188, 31, 194, 52, 186, 125, 169, 231, 119, 20, 117, 28, 31, 127, 8, 71, 237, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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