Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9606214eba92edfdb16e95051eca89549a12a4749b016618b20974c4de5e86e

Tx prefix hash: db13733458c081703b2a46ae978a0a15a5ba151c87c3a01430c8773ba369c391
Tx public key: 24c5061dcbc1cc9709e5284a9f621c9ed0d99332796d5625b6e538d14fd3c22b
Timestamp: 1755827334 Timestamp [UCT]: 2025-08-22 01:48:54 Age [y:d:h:m:s]: 00:096:16:09:19
Block: 1351654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69056 RingCT/type: yes/0
Extra: 0124c5061dcbc1cc9709e5284a9f621c9ed0d99332796d5625b6e538d14fd3c22b02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7e023cd9f7dda3f2512c81af354a28c761a0988ce5bbaf9c35d73a27d5b92aa 0.600000000000 1839611 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": 1351664, "vin": [ { "gen": { "height": 1351654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7e023cd9f7dda3f2512c81af354a28c761a0988ce5bbaf9c35d73a27d5b92aa" } } ], "extra": [ 1, 36, 197, 6, 29, 203, 193, 204, 151, 9, 229, 40, 74, 159, 98, 28, 158, 208, 217, 147, 50, 121, 109, 86, 37, 182, 229, 56, 209, 79, 211, 194, 43, 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