Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d9efd985fc17558f54cfed48e7704fb3ee71ed413741424f2ba8772a53e3c96

Tx prefix hash: aff05ea579e6f41e14db663c945ce004c24f0e7518f570bb6e2a181d6298a7f2
Tx public key: e0ce4d8574e5a904e747b8fce3c404d589ae6ed1a5f849378ce07b1bd46d3840
Timestamp: 1758525493 Timestamp [UTC]: 2025-09-22 07:18:13 Age [y:d:h:m:s]: 01:052:00:42:32
Block: 1373842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303407 RingCT/type: yes/0
Extra: 01e0ce4d8574e5a904e747b8fce3c404d589ae6ed1a5f849378ce07b1bd46d3840021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 242772286fd20b9a6e399bc46166b8ed214788164106f6a6270e2b3cfaf72c01 0.000600000000 1861927 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": 1373852, "vin": [ { "gen": { "height": 1373842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "242772286fd20b9a6e399bc46166b8ed214788164106f6a6270e2b3cfaf72c01" } } ], "extra": [ 1, 224, 206, 77, 133, 116, 229, 169, 4, 231, 71, 184, 252, 227, 196, 4, 213, 137, 174, 110, 209, 165, 248, 73, 55, 140, 224, 123, 27, 212, 109, 56, 64, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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: