Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b42b08b22ab2a0b1f051517b8da466d2c3d579a0f7013bdb347abd158328b35

Tx prefix hash: 9666ad3e88fd7c9a7462170935090251435d0d803ba3a2d9bc3f596151286764
Tx public key: 68f2f9b7ff5a533d1ae30c41bb0552ac39c3efc7e26fa870088702d83113149a
Timestamp: 1756114150 Timestamp [UCT]: 2025-08-25 09:29:10 Age [y:d:h:m:s]: 00:088:13:53:47
Block: 1354042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63232 RingCT/type: yes/0
Extra: 0168f2f9b7ff5a533d1ae30c41bb0552ac39c3efc7e26fa870088702d83113149a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d39e094db43b8670e10fcb8175a7cb5f3a998b36438a76978190d6a450dd3c 0.600000000000 1842023 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": 1354052, "vin": [ { "gen": { "height": 1354042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d39e094db43b8670e10fcb8175a7cb5f3a998b36438a76978190d6a450dd3c" } } ], "extra": [ 1, 104, 242, 249, 183, 255, 90, 83, 61, 26, 227, 12, 65, 187, 5, 82, 172, 57, 195, 239, 199, 226, 111, 168, 112, 8, 135, 2, 216, 49, 19, 20, 154, 2, 17, 0, 0, 0, 2, 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