Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856030c388108b44b7ac5d422ea2916ca4fb912d9097838ee367cb6ce1ae9b8b

Tx prefix hash: 9c70f3572f24dff798827a445e458060d379c3cc5ba22b2fc14fda55ec5f65e1
Tx public key: e52d731fc9a7e2b571d24bb88e81cae9001b4870e6270d56e020760c88b41d8e
Timestamp: 1763194614 Timestamp [UCT]: 2025-11-15 08:16:54 Age [y:d:h:m:s]: 00:013:01:17:43
Block: 1412525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9359 RingCT/type: yes/0
Extra: 01e52d731fc9a7e2b571d24bb88e81cae9001b4870e6270d56e020760c88b41d8e021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e64d42604438a0ae19a5fec8d852046a46b7a72439d57b558e4e40b239b157 0.600000000000 1900996 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": 1412535, "vin": [ { "gen": { "height": 1412525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e64d42604438a0ae19a5fec8d852046a46b7a72439d57b558e4e40b239b157" } } ], "extra": [ 1, 229, 45, 115, 31, 201, 167, 226, 181, 113, 210, 75, 184, 142, 129, 202, 233, 0, 27, 72, 112, 230, 39, 13, 86, 224, 32, 118, 12, 136, 180, 29, 142, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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