Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53d98e096d938a7bf25a976edd258c401dae528927e72bc2df66779c55a2fa3

Tx prefix hash: 90f92bdf46dae7812eb2d8c839891eb7b15766483d21666fa9c339be2a0c1667
Tx public key: 382e19b7f692e28d10c1b2113de597d54fe4c238c7150bdd2184a21282e24ec4
Timestamp: 1754129461 Timestamp [UCT]: 2025-08-02 10:11:01 Age [y:d:h:m:s]: 00:123:19:11:42
Block: 1338660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87391 RingCT/type: yes/0
Extra: 01382e19b7f692e28d10c1b2113de597d54fe4c238c7150bdd2184a21282e24ec402110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b54c07d0f59803bd2fce8e55fdceaf1505d88a751edae47f96faca1421643fb9 0.600000000000 1826469 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": 1338670, "vin": [ { "gen": { "height": 1338660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b54c07d0f59803bd2fce8e55fdceaf1505d88a751edae47f96faca1421643fb9" } } ], "extra": [ 1, 56, 46, 25, 183, 246, 146, 226, 141, 16, 193, 178, 17, 61, 229, 151, 213, 79, 228, 194, 56, 199, 21, 11, 221, 33, 132, 162, 18, 130, 226, 78, 196, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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