Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84059086329745204147be659292844b98e29f68109abe22ac0fea81dc1186da

Tx prefix hash: dc4b717bd2d2ff35f1e95d1d6e541be3fa0d5407429103ad6f742390fa0a1e50
Tx public key: 65b4c9f1b47eb3286bc3f209233d89f555a89da47050e0ba0a0a1d7cd4a6926a
Timestamp: 1707563585 Timestamp [UCT]: 2024-02-10 11:13:05 Age [y:d:h:m:s]: 01:040:11:14:03
Block: 954444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289969 RingCT/type: yes/0
Extra: 0165b4c9f1b47eb3286bc3f209233d89f555a89da47050e0ba0a0a1d7cd4a6926a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1ca0e4fdd642bbbe670ec288a93eb13a8d7e335d9682f3d852216db82d89ccc 0.600000000000 1413724 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": 954454, "vin": [ { "gen": { "height": 954444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1ca0e4fdd642bbbe670ec288a93eb13a8d7e335d9682f3d852216db82d89ccc" } } ], "extra": [ 1, 101, 180, 201, 241, 180, 126, 179, 40, 107, 195, 242, 9, 35, 61, 137, 245, 85, 168, 157, 164, 112, 80, 224, 186, 10, 10, 29, 124, 212, 166, 146, 106, 2, 17, 0, 0, 0, 2, 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