Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44150a4d5a2a31d5c5762d3e28652180b0c9f8ff0a1cc7e87d3d10a8924350e

Tx prefix hash: 47d0fba3baaf205365849064d110e38e8b18f0cf44c1930caa8b7b6ea931794b
Tx public key: 5dc6ea22753177a4f8c0cc21199823b8628ac5820987ca13126ab38d245dedee
Timestamp: 1720989897 Timestamp [UCT]: 2024-07-14 20:44:57 Age [y:d:h:m:s]: 00:297:04:28:25
Block: 1065769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212339 RingCT/type: yes/0
Extra: 015dc6ea22753177a4f8c0cc21199823b8628ac5820987ca13126ab38d245dedee02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c57e2252ab9caaeabc5bdd964c5816dc5add474d3360b823b061b974a618df2 0.600000000000 1536320 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": 1065779, "vin": [ { "gen": { "height": 1065769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c57e2252ab9caaeabc5bdd964c5816dc5add474d3360b823b061b974a618df2" } } ], "extra": [ 1, 93, 198, 234, 34, 117, 49, 119, 164, 248, 192, 204, 33, 25, 152, 35, 184, 98, 138, 197, 130, 9, 135, 202, 19, 18, 106, 179, 141, 36, 93, 237, 238, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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