Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855311c623f956b657a90cf943ffcc43f12a38661fdc0f073436b425b59ee0de

Tx prefix hash: 52766796fb052c4a700d74f4b76f2344a92d98904b5d1728d853fdc259769589
Tx public key: 7e65e9866fb917a4799e6a4a268dc1b52019c6207646744e29f6249f6c9f6df3
Timestamp: 1579292949 Timestamp [UCT]: 2020-01-17 20:29:09 Age [y:d:h:m:s]: 04:347:19:20:13
Block: 47846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137967 RingCT/type: yes/0
Extra: 017e65e9866fb917a4799e6a4a268dc1b52019c6207646744e29f6249f6c9f6df30211000000074943cd9f000000000000000000

1 output(s) for total of 426.056481307000 dcy

stealth address amount amount idx
00: ae649ca59f4997d56677ae0d02906af60cd5fb2b174b9050e7f4003e637b586b 426.056481307000 88387 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": 47856, "vin": [ { "gen": { "height": 47846 } } ], "vout": [ { "amount": 426056481307, "target": { "key": "ae649ca59f4997d56677ae0d02906af60cd5fb2b174b9050e7f4003e637b586b" } } ], "extra": [ 1, 126, 101, 233, 134, 111, 185, 23, 164, 121, 158, 106, 74, 38, 141, 193, 181, 32, 25, 198, 32, 118, 70, 116, 78, 41, 246, 36, 159, 108, 159, 109, 243, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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