Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 121a4a8e71d88dda8bbfa7c4ef6287898a70f22913d50e7a8aebc89ddb88aa3e

Tx prefix hash: a91cd4c3549fe1ae7be4c3c69c010098166c776da5750905aa536d987bbc3211
Tx public key: 77e880c5b2e63a0a598170eabad873e340b4cd11ab0cc02be3345443dd7f75b0
Timestamp: 1758879582 Timestamp [UTC]: 2025-09-26 09:39:42 Age [y:d:h:m:s]: 01:047:20:54:52
Block: 1376783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300426 RingCT/type: yes/0
Extra: 0177e880c5b2e63a0a598170eabad873e340b4cd11ab0cc02be3345443dd7f75b00211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cc28513e9accf47dab42afbb35ca5d7d5db5a1784124c7eea0d18eaa6577e6a6 0.000600000000 1864874 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 dinastycoin-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": 1376793, "vin": [ { "gen": { "height": 1376783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc28513e9accf47dab42afbb35ca5d7d5db5a1784124c7eea0d18eaa6577e6a6" } } ], "extra": [ 1, 119, 232, 128, 197, 178, 230, 58, 10, 89, 129, 112, 234, 186, 216, 115, 227, 64, 180, 205, 17, 171, 12, 192, 43, 227, 52, 84, 67, 221, 127, 117, 176, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: