Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83fea68218f1678e86549ad5034b526363bafa22a35f6b02470fc1935dbb3d5f

Tx prefix hash: 676321941d0dcc5c3d5d788b2f6f172d215ed84e54c6de6c2b6b47a430d31025
Tx public key: a566179783e44250c6b8481f84b058510028df2baefd8db652b386106f3dffb6
Timestamp: 1577824105 Timestamp [UCT]: 2019-12-31 20:28:25 Age [y:d:h:m:s]: 05:002:09:41:11
Block: 35998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151681 RingCT/type: yes/0
Extra: 01a566179783e44250c6b8481f84b058510028df2baefd8db652b386106f3dffb6021100000042ac34bf9e000000000000000000

1 output(s) for total of 466.363481798000 dcy

stealth address amount amount idx
00: b3357e5fd2a48c3b4a1efe2b925b724adf4fe609330e10237ed0ba41b287c04d 466.363481798000 60818 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": 36008, "vin": [ { "gen": { "height": 35998 } } ], "vout": [ { "amount": 466363481798, "target": { "key": "b3357e5fd2a48c3b4a1efe2b925b724adf4fe609330e10237ed0ba41b287c04d" } } ], "extra": [ 1, 165, 102, 23, 151, 131, 228, 66, 80, 198, 184, 72, 31, 132, 176, 88, 81, 0, 40, 223, 43, 174, 253, 141, 182, 82, 179, 134, 16, 111, 61, 255, 182, 2, 17, 0, 0, 0, 66, 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