Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a7a38858c13a4dd773e7754ec6877c00d86dda1b4ad818d195b4bb869c47bc7

Tx prefix hash: ac5cf86cfa64c4693f29d675591b9a7b9b288a579119a5d111052fad50c51123
Tx public key: 9dec5cbcb0a2c347e56d993e91832cef3f8bd3dde6592ae39acd4471a3f76982
Timestamp: 1707427154 Timestamp [UCT]: 2024-02-08 21:19:14 Age [y:d:h:m:s]: 00:223:19:32:19
Block: 953314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160323 RingCT/type: yes/0
Extra: 019dec5cbcb0a2c347e56d993e91832cef3f8bd3dde6592ae39acd4471a3f76982021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b506608f2ce5a3b70026816e62c223314993089d1f1819af000aeda0a3d672e 0.600000000000 1412508 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": 953324, "vin": [ { "gen": { "height": 953314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b506608f2ce5a3b70026816e62c223314993089d1f1819af000aeda0a3d672e" } } ], "extra": [ 1, 157, 236, 92, 188, 176, 162, 195, 71, 229, 109, 153, 62, 145, 131, 44, 239, 63, 139, 211, 221, 230, 89, 42, 227, 154, 205, 68, 113, 163, 247, 105, 130, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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