Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36fa55160899a1f9fd2604422cbe8145d5154ff9327eb57d30fd5657afc3a762

Tx prefix hash: fb50e060f97a283e29d18b6d6e3d27a46a5da4797ca2bd0234af586bcd5063eb
Tx public key: cbad4afb51191812da4a4a0eb11b07154c99cc7b35342e1c3e2c2ee94cdf2089
Timestamp: 1741827913 Timestamp [UCT]: 2025-03-13 01:05:13 Age [y:d:h:m:s]: 00:251:23:24:10
Block: 1238061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177822 RingCT/type: yes/0
Extra: 01cbad4afb51191812da4a4a0eb11b07154c99cc7b35342e1c3e2c2ee94cdf2089021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a463ae4f0d854c99cf32b1c49c97d98e8eec3db593d9023fde76c313df4c287b 0.600000000000 1725020 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": 1238071, "vin": [ { "gen": { "height": 1238061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a463ae4f0d854c99cf32b1c49c97d98e8eec3db593d9023fde76c313df4c287b" } } ], "extra": [ 1, 203, 173, 74, 251, 81, 25, 24, 18, 218, 74, 74, 14, 177, 27, 7, 21, 76, 153, 204, 123, 53, 52, 46, 28, 62, 44, 46, 233, 76, 223, 32, 137, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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