Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 814e705224602d0360e2cdcdb1a9701d02edcd1716d1e303f6f3f1dcbf070b10

Tx prefix hash: 7357773f14d524722e0dd95538d14f168bdb6eaabeea2cd1c3409d4e21389015
Tx public key: e27550b4a862d55b8e489503316a4403e9ad010058bc2d0fc5bd3a9e0afd5a74
Timestamp: 1704378208 Timestamp [UCT]: 2024-01-04 14:23:28 Age [y:d:h:m:s]: 01:315:07:01:16
Block: 928045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484171 RingCT/type: yes/0
Extra: 01e27550b4a862d55b8e489503316a4403e9ad010058bc2d0fc5bd3a9e0afd5a7402110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c00412a554d1364a79a2d02372092d854d3430bf7f5c688aa90efc67797108dd 0.600000000000 1385901 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": 928055, "vin": [ { "gen": { "height": 928045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c00412a554d1364a79a2d02372092d854d3430bf7f5c688aa90efc67797108dd" } } ], "extra": [ 1, 226, 117, 80, 180, 168, 98, 213, 91, 142, 72, 149, 3, 49, 106, 68, 3, 233, 173, 1, 0, 88, 188, 45, 15, 197, 189, 58, 158, 10, 253, 90, 116, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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