Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34ede3bbd299bbe760020749a121afa6cb4ebfe2f5df42e2e995a070b5a9529

Tx prefix hash: 7b9cea5e47482ffa3a8c6233e845795fd7fb48d9338087d3860e53430bcd5327
Tx public key: da37490affd6d975a8b2b90f75864facbae8f2fbc733da653a3f2dc3d52e1d2e
Timestamp: 1760324788 Timestamp [UCT]: 2025-10-13 03:06:28 Age [y:d:h:m:s]: 00:074:15:04:39
Block: 1388752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53430 RingCT/type: yes/0
Extra: 01da37490affd6d975a8b2b90f75864facbae8f2fbc733da653a3f2dc3d52e1d2e02110000000725a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 589776c833b417fe23925b4ac789e67ac1b64627226ab8868afdd3b9114d8ddc 0.600000000000 1876975 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": 1388762, "vin": [ { "gen": { "height": 1388752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "589776c833b417fe23925b4ac789e67ac1b64627226ab8868afdd3b9114d8ddc" } } ], "extra": [ 1, 218, 55, 73, 10, 255, 214, 217, 117, 168, 178, 185, 15, 117, 134, 79, 172, 186, 232, 242, 251, 199, 51, 218, 101, 58, 63, 45, 195, 213, 46, 29, 46, 2, 17, 0, 0, 0, 7, 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