Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2db32be32c7cba6f066972da936f919c1cc69e4eef00da8cbd59fe4ab4b0ca2

Tx prefix hash: a162721903afad092d2bac637bb4f95ed24dc080c5d012e53490504a15c5ad71
Tx public key: 85b8ecbbf86ea8630ed3e729c19801790cfc22dc40e2e1784ed9a0a2304b870d
Timestamp: 1704885797 Timestamp [UCT]: 2024-01-10 11:23:17 Age [y:d:h:m:s]: 01:097:20:47:39
Block: 932243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331046 RingCT/type: yes/0
Extra: 0185b8ecbbf86ea8630ed3e729c19801790cfc22dc40e2e1784ed9a0a2304b870d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5de4d28f1516d46385cbedc19af1da8b96e51628f552d65b83904ee2fc1660a 0.600000000000 1390173 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": 932253, "vin": [ { "gen": { "height": 932243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5de4d28f1516d46385cbedc19af1da8b96e51628f552d65b83904ee2fc1660a" } } ], "extra": [ 1, 133, 184, 236, 187, 248, 110, 168, 99, 14, 211, 231, 41, 193, 152, 1, 121, 12, 252, 34, 220, 64, 226, 225, 120, 78, 217, 160, 162, 48, 75, 135, 13, 2, 17, 0, 0, 0, 1, 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