Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f51fb21ca2c782da7f00b9e29390c983b71353eb61c52aa56be0e01a0e138ee

Tx prefix hash: 274497576e23cfa1920ecc496848c3ac05283b9636ae165f3f13b49345935768
Tx public key: fdc8cca3c3479686089267fedaa2973fad42ea278a840f1b936cfd0f7101d79e
Timestamp: 1755498504 Timestamp [UCT]: 2025-08-18 06:28:24 Age [y:d:h:m:s]: 00:088:18:47:41
Block: 1349013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63312 RingCT/type: yes/0
Extra: 01fdc8cca3c3479686089267fedaa2973fad42ea278a840f1b936cfd0f7101d79e0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c405c9ba15dc65f679ae72f77ae024181621073c9d08bd1b2aa8b1a5f732aa50 0.600000000000 1836942 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": 1349023, "vin": [ { "gen": { "height": 1349013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c405c9ba15dc65f679ae72f77ae024181621073c9d08bd1b2aa8b1a5f732aa50" } } ], "extra": [ 1, 253, 200, 204, 163, 195, 71, 150, 134, 8, 146, 103, 254, 218, 162, 151, 63, 173, 66, 234, 39, 138, 132, 15, 27, 147, 108, 253, 15, 113, 1, 215, 158, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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