Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea14f824348ab612182be4262eb79c216a119735cb19535742f7239560f5097b

Tx prefix hash: 3680bc6decb834921f357b2fe3aab607ae01bff8e576d77806f1ebc8c8b14ebf
Tx public key: d95a6c2a0033b705fd4cbc5413870a330c2d108bb48d3af892b3bcc3def86d28
Timestamp: 1702934007 Timestamp [UCT]: 2023-12-18 21:13:27 Age [y:d:h:m:s]: 02:004:08:32:47
Block: 916070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522877 RingCT/type: yes/0
Extra: 01d95a6c2a0033b705fd4cbc5413870a330c2d108bb48d3af892b3bcc3def86d28021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb7cde7f138ec9e8a2a97b9bde63f7d6351e573962742931c01da932b3f9e01 0.600000000000 1373544 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": 916080, "vin": [ { "gen": { "height": 916070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb7cde7f138ec9e8a2a97b9bde63f7d6351e573962742931c01da932b3f9e01" } } ], "extra": [ 1, 217, 90, 108, 42, 0, 51, 183, 5, 253, 76, 188, 84, 19, 135, 10, 51, 12, 45, 16, 139, 180, 141, 58, 248, 146, 179, 188, 195, 222, 248, 109, 40, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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