Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b89683ea39a90d39837768aa8620d6d2e09a4094640fdc33480ffedcf16bb3

Tx prefix hash: 56437f456aa4a5d61521067a50efafc623a046029674c041bae8ce27555d3e05
Tx public key: 182dd1a313fb72d2150f87f279a36a80486d3e96d924d071eaa35a828463cf58
Timestamp: 1719214598 Timestamp [UCT]: 2024-06-24 07:36:38 Age [y:d:h:m:s]: 00:283:15:45:27
Block: 1051034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202696 RingCT/type: yes/0
Extra: 01182dd1a313fb72d2150f87f279a36a80486d3e96d924d071eaa35a828463cf5802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62c36cf8c3f905c0d5df2a2eeea7f9537ce5ee910f8170e53cae936e095b126d 0.600000000000 1521221 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": 1051044, "vin": [ { "gen": { "height": 1051034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62c36cf8c3f905c0d5df2a2eeea7f9537ce5ee910f8170e53cae936e095b126d" } } ], "extra": [ 1, 24, 45, 209, 163, 19, 251, 114, 210, 21, 15, 135, 242, 121, 163, 106, 128, 72, 109, 62, 150, 217, 36, 208, 113, 234, 163, 90, 130, 132, 99, 207, 88, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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