Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d62e6929b4b7c4de90bbf6ee6c926e6f7b113588b63be6ebfa2ca3f1dcbd7485

Tx prefix hash: 6dc941559a261e1a1a401ed6fd02d1c25ebbc66eb9127104a816f611303c30d3
Tx public key: 15035fd0904d88645c3bf3295b12ec5de7d668afc0cbc56a54dd253c57c7e58d
Timestamp: 1775160330 Timestamp [UTC]: 2026-04-02 20:05:30 Age [y:d:h:m:s]: 00:225:15:47:02
Block: 1511445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166670 RingCT/type: yes/0
Extra: 0115035fd0904d88645c3bf3295b12ec5de7d668afc0cbc56a54dd253c57c7e58d02110000000143b50471000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d07b9df9e1fcc1dd707b71b089e7a4fb4a49a6ac5dcffd9d6a478a85f760d47d 0.000600000000 2001237 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": 1511455, "vin": [ { "gen": { "height": 1511445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d07b9df9e1fcc1dd707b71b089e7a4fb4a49a6ac5dcffd9d6a478a85f760d47d" } } ], "extra": [ 1, 21, 3, 95, 208, 144, 77, 136, 100, 92, 59, 243, 41, 91, 18, 236, 93, 231, 214, 104, 175, 192, 203, 197, 106, 84, 221, 37, 60, 87, 199, 229, 141, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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: