Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79542086c30bc0af198a2ba7e3caf7190c88b0b909e473b693ca4524620decdc

Tx prefix hash: 6db7c82eb285470fce8e6b2d75278a676dc011fe6385cdc290095f88583e2f73
Tx public key: 7972744e7e9ecc9baa5ca0b5bec2baefb061d23ac5da7f7b3e1e46db01e00dbd
Timestamp: 1760428568 Timestamp [UCT]: 2025-10-14 07:56:08 Age [y:d:h:m:s]: 00:111:05:54:58
Block: 1389614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79476 RingCT/type: yes/0
Extra: 017972744e7e9ecc9baa5ca0b5bec2baefb061d23ac5da7f7b3e1e46db01e00dbd0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e460c4a802f266dfdac695649327c6b140a698e43ad5148617b54c6182da4c90 0.600000000000 1877843 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": 1389624, "vin": [ { "gen": { "height": 1389614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e460c4a802f266dfdac695649327c6b140a698e43ad5148617b54c6182da4c90" } } ], "extra": [ 1, 121, 114, 116, 78, 126, 158, 204, 155, 170, 92, 160, 181, 190, 194, 186, 239, 176, 97, 210, 58, 197, 218, 127, 123, 62, 30, 70, 219, 1, 224, 13, 189, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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