Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3a1fbaae6d417a7d19547af75a3666b4d09e1c5eba728c836db223e08a480e

Tx prefix hash: fc936836466a2e6bb4ec189ea4beb2e072399b71d3bd2a812a4069df5c8bf84f
Tx public key: 71e8b43842098ea3e4442101181b3bc89a42e72926e2cfffc3aae47a758477c3
Timestamp: 1698458937 Timestamp [UCT]: 2023-10-28 02:08:57 Age [y:d:h:m:s]: 01:171:13:35:07
Block: 879187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383621 RingCT/type: yes/0
Extra: 0171e8b43842098ea3e4442101181b3bc89a42e72926e2cfffc3aae47a758477c3021100000002faf35c9c000000000000000000

1 output(s) for total of 0.749701733000 dcy

stealth address amount amount idx
00: 6e6c5417b701de5a4c646d4da97d01dc6de1d2766e0a7b820950122f60233b0e 0.749701733000 1334691 of 0

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": 879197, "vin": [ { "gen": { "height": 879187 } } ], "vout": [ { "amount": 749701733, "target": { "key": "6e6c5417b701de5a4c646d4da97d01dc6de1d2766e0a7b820950122f60233b0e" } } ], "extra": [ 1, 113, 232, 180, 56, 66, 9, 142, 163, 228, 68, 33, 1, 24, 27, 59, 200, 154, 66, 231, 41, 38, 226, 207, 255, 195, 170, 228, 122, 117, 132, 119, 195, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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