Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b7a2f19a05b73707b3c25636bdd682ec899ad1f8334fc1e821e3f75912e8cee

Tx prefix hash: d9c8d5aab9112843ce20ce7f5a2818dcba227200a9b2d1fbccc26ac7d13b78ce
Tx public key: 64a3e8606beaf7bbfd3ff60ea07f781566d59fea88e5e3d06312746462b0ac31
Timestamp: 1724500502 Timestamp [UCT]: 2024-08-24 11:55:02 Age [y:d:h:m:s]: 00:285:04:22:14
Block: 1094877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203734 RingCT/type: yes/0
Extra: 0164a3e8606beaf7bbfd3ff60ea07f781566d59fea88e5e3d06312746462b0ac3102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec228302837b96806124cdf6527d092a1ce1b27a9a0b4393690dbc58d76298c9 0.600000000000 1569998 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": 1094887, "vin": [ { "gen": { "height": 1094877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec228302837b96806124cdf6527d092a1ce1b27a9a0b4393690dbc58d76298c9" } } ], "extra": [ 1, 100, 163, 232, 96, 107, 234, 247, 187, 253, 63, 246, 14, 160, 127, 120, 21, 102, 213, 159, 234, 136, 229, 227, 208, 99, 18, 116, 100, 98, 176, 172, 49, 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