Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95717fe1b0b350880b47584af6d49206c35bca3518f2baba6cac74766aac08ac

Tx prefix hash: 8754f6e6c9ed6cfab93ac1bfc8fad5108f843a10d5d5c9aeb6cea13020940b64
Tx public key: 9ea55f01c5774e6b876d5f17dfb96cdafe5b222f18e4343c4acb2a8900cfc1c2
Timestamp: 1632169330 Timestamp [UCT]: 2021-09-20 20:22:10 Age [y:d:h:m:s]: 03:099:13:06:05
Block: 337749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 847166 RingCT/type: yes/0
Extra: 019ea55f01c5774e6b876d5f17dfb96cdafe5b222f18e4343c4acb2a8900cfc1c20211000000225d7cc334000000000000000000

1 output(s) for total of 46.654956857000 dcy

stealth address amount amount idx
00: e73c643c0800e869a01866c9a5406b3ff93f6445481e316d7c334c2d9204940c 46.654956857000 695360 of 0

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": 337759, "vin": [ { "gen": { "height": 337749 } } ], "vout": [ { "amount": 46654956857, "target": { "key": "e73c643c0800e869a01866c9a5406b3ff93f6445481e316d7c334c2d9204940c" } } ], "extra": [ 1, 158, 165, 95, 1, 197, 119, 78, 107, 135, 109, 95, 23, 223, 185, 108, 218, 254, 91, 34, 47, 24, 228, 52, 60, 74, 203, 42, 137, 0, 207, 193, 194, 2, 17, 0, 0, 0, 34, 93, 124, 195, 52, 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