Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e845ca67d6f0283ee3d215f95578b1c05dfe55519c3d10dae530d81c5f7d5a4

Tx prefix hash: c15fb06bff26f57a7c4b53136cab7010f5cfd6406e84fa0a16e2e4e80c2bbc20
Tx public key: 6a346420ed132a9938da54421045acc8e0a9773990d2c97e9e871b520144aea1
Timestamp: 1722355698 Timestamp [UCT]: 2024-07-30 16:08:18 Age [y:d:h:m:s]: 00:175:20:44:41
Block: 1077079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125786 RingCT/type: yes/0
Extra: 016a346420ed132a9938da54421045acc8e0a9773990d2c97e9e871b520144aea102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b9f35324e2380e27882c38be807567b6840cfce36a889d2b99b66bb0622623f 0.600000000000 1549622 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": 1077089, "vin": [ { "gen": { "height": 1077079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b9f35324e2380e27882c38be807567b6840cfce36a889d2b99b66bb0622623f" } } ], "extra": [ 1, 106, 52, 100, 32, 237, 19, 42, 153, 56, 218, 84, 66, 16, 69, 172, 200, 224, 169, 119, 57, 144, 210, 201, 126, 158, 135, 27, 82, 1, 68, 174, 161, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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