Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4ec8a1d7ae34c3ef0fe61a2fddf37b504ee40be3ba1694febedc3ba580c68d5

Tx prefix hash: 17212326bb0ab3209aff64976041dce16dd6546ec5953b3d5cc8dde51a5bab46
Tx public key: 2341c9b3b63d8afad440c5c5f96e7577292f900a7fc09f9ba950c9b1e46d8f01
Timestamp: 1728115408 Timestamp [UCT]: 2024-10-05 08:03:28 Age [y:d:h:m:s]: 00:260:20:00:59
Block: 1124837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186053 RingCT/type: yes/0
Extra: 012341c9b3b63d8afad440c5c5f96e7577292f900a7fc09f9ba950c9b1e46d8f01021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bafbc05923159535881750a6d214aa07e0e3d349b6102a531ecfcc3b30752f57 0.600000000000 1607508 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": 1124847, "vin": [ { "gen": { "height": 1124837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bafbc05923159535881750a6d214aa07e0e3d349b6102a531ecfcc3b30752f57" } } ], "extra": [ 1, 35, 65, 201, 179, 182, 61, 138, 250, 212, 64, 197, 197, 249, 110, 117, 119, 41, 47, 144, 10, 127, 192, 159, 155, 169, 80, 201, 177, 228, 109, 143, 1, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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