Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c3c2d445a97f618b2a3971eca7eb7e612f0e9ee17d1467079c72becab8e631

Tx prefix hash: d2a16adc2796cf66eb1437f81c210501f30a4d71f9471bb0f79a2086809e68e3
Tx public key: 70c51929607319003dfe4cdd4871c388d0be6a70afbe247c07d7c3cd71dcb274
Timestamp: 1763106958 Timestamp [UCT]: 2025-11-14 07:55:58 Age [y:d:h:m:s]: 00:047:18:00:48
Block: 1411813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34188 RingCT/type: yes/0
Extra: 0170c51929607319003dfe4cdd4871c388d0be6a70afbe247c07d7c3cd71dcb274021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc85c0ad7fd27b281ad3a10e68eeab268ed1ba654ba0066d790584d21577ca1e 0.600000000000 1900278 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": 1411823, "vin": [ { "gen": { "height": 1411813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc85c0ad7fd27b281ad3a10e68eeab268ed1ba654ba0066d790584d21577ca1e" } } ], "extra": [ 1, 112, 197, 25, 41, 96, 115, 25, 0, 61, 254, 76, 221, 72, 113, 195, 136, 208, 190, 106, 112, 175, 190, 36, 124, 7, 215, 195, 205, 113, 220, 178, 116, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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