Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1019938612f9d5d9861c676564a1503aa838ba69bf8b9f50cdb0220a8798a0f9

Tx prefix hash: de9a75c89b7d21bcfe0cbc791c821fa1501601bee1e67bfbae39e3dd7c65054d
Tx public key: 140de452f3a1e3456a24dd25323f41cf48277dcea1fa0a2289e63c9b303b4336
Timestamp: 1750507904 Timestamp [UCT]: 2025-06-21 12:11:44 Age [y:d:h:m:s]: 00:150:10:59:50
Block: 1309740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105383 RingCT/type: yes/0
Extra: 01140de452f3a1e3456a24dd25323f41cf48277dcea1fa0a2289e63c9b303b4336021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb9564d24f9b1c0cbccab9057de654aa54984e5239acd5f07182a75c2b0186b 0.600000000000 1797357 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": 1309750, "vin": [ { "gen": { "height": 1309740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb9564d24f9b1c0cbccab9057de654aa54984e5239acd5f07182a75c2b0186b" } } ], "extra": [ 1, 20, 13, 228, 82, 243, 161, 227, 69, 106, 36, 221, 37, 50, 63, 65, 207, 72, 39, 125, 206, 161, 250, 10, 34, 137, 230, 60, 155, 48, 59, 67, 54, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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