Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e448fd915db8be7495489a484464f4fae02bb2bc4745e39bd4b55ed8ec99eae

Tx prefix hash: bfd1a4ad8564269acdfa4c3805df0d556086c8629558e3cee3317c5ecbae2a98
Tx public key: 7d80b042ce2bcf88f9a2ea3c46a48a81dd5250528dda1b36eda15ba76c91d7d9
Timestamp: 1703534547 Timestamp [UCT]: 2023-12-25 20:02:27 Age [y:d:h:m:s]: 01:163:08:16:41
Block: 921053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377895 RingCT/type: yes/0
Extra: 017d80b042ce2bcf88f9a2ea3c46a48a81dd5250528dda1b36eda15ba76c91d7d902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e86d9862ac18c0657205002edb94d26e62e197e7401f48a7faf8779f9ebb1858 0.600000000000 1378737 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": 921063, "vin": [ { "gen": { "height": 921053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e86d9862ac18c0657205002edb94d26e62e197e7401f48a7faf8779f9ebb1858" } } ], "extra": [ 1, 125, 128, 176, 66, 206, 43, 207, 136, 249, 162, 234, 60, 70, 164, 138, 129, 221, 82, 80, 82, 141, 218, 27, 54, 237, 161, 91, 167, 108, 145, 215, 217, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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