Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5a3b172bb616e85ec0562d0e20e72fcd7147ee7ffeaf1b70b538bfab81c458

Tx prefix hash: 1e7577905e921980196f8bc5048e9bdfb3e0d184a8dd66d6ef3d23d4b8b458ea
Tx public key: bfef0a7e38b3fb52283b58a77856e1adcca6f0a8ae269ecfe2e5e0255f4fd1e5
Timestamp: 1724602500 Timestamp [UCT]: 2024-08-25 16:15:00 Age [y:d:h:m:s]: 00:208:19:54:06
Block: 1095721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149100 RingCT/type: yes/0
Extra: 01bfef0a7e38b3fb52283b58a77856e1adcca6f0a8ae269ecfe2e5e0255f4fd1e502110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c0f556cf36e942065875ca909433b6048b72fe041fd06cad7f16728a1e1e8d1 0.600000000000 1570902 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": 1095731, "vin": [ { "gen": { "height": 1095721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c0f556cf36e942065875ca909433b6048b72fe041fd06cad7f16728a1e1e8d1" } } ], "extra": [ 1, 191, 239, 10, 126, 56, 179, 251, 82, 40, 59, 88, 167, 120, 86, 225, 173, 204, 166, 240, 168, 174, 38, 158, 207, 226, 229, 224, 37, 95, 79, 209, 229, 2, 17, 0, 0, 0, 14, 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