Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a89671c905053f8c0a1c0916534077f4421a5e5f6b601ce870236a53c472360

Tx prefix hash: 04588e828441bcd3e616a4caf77dbafd5e3568dacf9acb04202c6cac5a730c9d
Tx public key: 98ed392967ca004a800b42c1ce29f76dc93c3d8ed8be47e894e3e41a0858e943
Timestamp: 1577404699 Timestamp [UCT]: 2019-12-26 23:58:19 Age [y:d:h:m:s]: 04:315:21:03:40
Block: 32514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114817 RingCT/type: yes/0
Extra: 0198ed392967ca004a800b42c1ce29f76dc93c3d8ed8be47e894e3e41a0858e9430211000000deac34bf9e000000000000000000

1 output(s) for total of 478.967381324000 dcy

stealth address amount amount idx
00: a4ad2707eacc9eae1969f1584dbc14e0b39cfbdee3570c3ee649aedcb1865a01 478.967381324000 54093 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": 32524, "vin": [ { "gen": { "height": 32514 } } ], "vout": [ { "amount": 478967381324, "target": { "key": "a4ad2707eacc9eae1969f1584dbc14e0b39cfbdee3570c3ee649aedcb1865a01" } } ], "extra": [ 1, 152, 237, 57, 41, 103, 202, 0, 74, 128, 11, 66, 193, 206, 41, 247, 109, 201, 60, 61, 142, 216, 190, 71, 232, 148, 227, 228, 26, 8, 88, 233, 67, 2, 17, 0, 0, 0, 222, 172, 52, 191, 158, 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