Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eef54ece686862360b65ce2337cd4a87d86131197a175597c6f08cc614348b7

Tx prefix hash: 445afdecb7d41d1dbd034eb494e272f4f39cf01ba37df78f4f45f9dcc38b5789
Tx public key: 1dcd11c2116ed733fa20f1dafc6a1cd6017abd5d006aaf2473ebc837d842e3b2
Timestamp: 1760298071 Timestamp [UCT]: 2025-10-12 19:41:11 Age [y:d:h:m:s]: 00:039:12:05:31
Block: 1388528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28272 RingCT/type: yes/0
Extra: 011dcd11c2116ed733fa20f1dafc6a1cd6017abd5d006aaf2473ebc837d842e3b20211000000015175c842000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9a7e7fb791cbc9df22404770c6e50a19f456416b8c9e53a3deea5b716e810e4 0.600000000000 1876743 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": 1388538, "vin": [ { "gen": { "height": 1388528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9a7e7fb791cbc9df22404770c6e50a19f456416b8c9e53a3deea5b716e810e4" } } ], "extra": [ 1, 29, 205, 17, 194, 17, 110, 215, 51, 250, 32, 241, 218, 252, 106, 28, 214, 1, 122, 189, 93, 0, 106, 175, 36, 115, 235, 200, 55, 216, 66, 227, 178, 2, 17, 0, 0, 0, 1, 81, 117, 200, 66, 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