Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95d104af3f63642de1efdc5e645a37fd5e3a70baa011484bbefcfb84d657101c

Tx prefix hash: 5645f1664b786d25952065a6f42c63c642de5542903065cb5a8bec45d118b4b0
Tx public key: d10c6c37ad6a6c27142582cc3a3b641f95fb28f5997f9a10eab0cd0b29f7794c
Timestamp: 1708241010 Timestamp [UCT]: 2024-02-18 07:23:30 Age [y:d:h:m:s]: 01:006:13:38:39
Block: 960061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265691 RingCT/type: yes/0
Extra: 01d10c6c37ad6a6c27142582cc3a3b641f95fb28f5997f9a10eab0cd0b29f7794c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fcbd11729355504eee6dfe0666222fa8f45c831faa43e78ad61504fdd4fc91b 0.600000000000 1419620 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": 960071, "vin": [ { "gen": { "height": 960061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fcbd11729355504eee6dfe0666222fa8f45c831faa43e78ad61504fdd4fc91b" } } ], "extra": [ 1, 209, 12, 108, 55, 173, 106, 108, 39, 20, 37, 130, 204, 58, 59, 100, 31, 149, 251, 40, 245, 153, 127, 154, 16, 234, 176, 205, 11, 41, 247, 121, 76, 2, 17, 0, 0, 0, 1, 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