Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbfd1e2310d7694fd16ef8931fbf0fc4c2d34b89326755ed14d9bbffd4c2a78

Tx prefix hash: a794de68a9e79a5e1c2013844e81643af036eef8f598b7fb87d88162bd5d637b
Tx public key: 37e370c22552e761d91bd266f89b377dfa0abad004c0ad7e96bc8e3d17805f3c
Timestamp: 1755434032 Timestamp [UCT]: 2025-08-17 12:33:52 Age [y:d:h:m:s]: 00:096:05:15:50
Block: 1348498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68606 RingCT/type: yes/0
Extra: 0137e370c22552e761d91bd266f89b377dfa0abad004c0ad7e96bc8e3d17805f3c021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c4347ab3609d753b8b36ce11f50e46199fd4571fe4e5b0ffa3aa78cb17e950d 0.600000000000 1836425 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": 1348508, "vin": [ { "gen": { "height": 1348498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c4347ab3609d753b8b36ce11f50e46199fd4571fe4e5b0ffa3aa78cb17e950d" } } ], "extra": [ 1, 55, 227, 112, 194, 37, 82, 231, 97, 217, 27, 210, 102, 248, 155, 55, 125, 250, 10, 186, 208, 4, 192, 173, 126, 150, 188, 142, 61, 23, 128, 95, 60, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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