Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0db2b9b0c439ea51d8441ca43150ed3b8da3c8bdd1dbe7075615a2f322d2c4ac

Tx prefix hash: d35cde275479d7e57852df23bcc927d449847938053be7c5693dea9f054d3fe4
Tx public key: 495b90104876f3c22b5e9bffd607a26c1b8df4283985e566bd24a9b3b4b86d3a
Timestamp: 1770332441 Timestamp [UTC]: 2026-02-05 23:00:41 Age [y:d:h:m:s]: 00:282:02:10:42
Block: 1471530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 206996 RingCT/type: yes/0
Extra: 01495b90104876f3c22b5e9bffd607a26c1b8df4283985e566bd24a9b3b4b86d3a02087f424b0ae8cbc546

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d646b051205bfe2d6a00947e9c1642fd50583650ee190ef2c5d46088e836f16e 0.000600000000 1960802 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": 1471540, "vin": [ { "gen": { "height": 1471530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d646b051205bfe2d6a00947e9c1642fd50583650ee190ef2c5d46088e836f16e" } } ], "extra": [ 1, 73, 91, 144, 16, 72, 118, 243, 194, 43, 94, 155, 255, 214, 7, 162, 108, 27, 141, 244, 40, 57, 133, 229, 102, 189, 36, 169, 179, 180, 184, 109, 58, 2, 8, 127, 66, 75, 10, 232, 203, 197, 70 ], "rct_signatures": { "type": 0 } }


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