Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6f273f60f3c3a0df9a3986cd08ce856a48ffc5d6e749b9b2c7080d2ad4c324

Tx prefix hash: 50d26c7082f20924179198c723262848480d2494e1afc37dd9426f8d2d57935a
Tx public key: 961148867611622dce5dfe306307d5f7262e4b6e704e3d5b170a9ef3c6b95279
Timestamp: 1749007354 Timestamp [UTC]: 2025-06-04 03:22:34 Age [y:d:h:m:s]: 01:164:07:41:11
Block: 1297499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381346 RingCT/type: yes/0
Extra: 01961148867611622dce5dfe306307d5f7262e4b6e704e3d5b170a9ef3c6b9527902110000000143846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf0241bd51816431c6a66861ed0907db3d31464bbb6c0ae1b1d91bc6de35de14 0.000600000000 1785018 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": 1297509, "vin": [ { "gen": { "height": 1297499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf0241bd51816431c6a66861ed0907db3d31464bbb6c0ae1b1d91bc6de35de14" } } ], "extra": [ 1, 150, 17, 72, 134, 118, 17, 98, 45, 206, 93, 254, 48, 99, 7, 213, 247, 38, 46, 75, 110, 112, 78, 61, 91, 23, 10, 158, 243, 198, 185, 82, 121, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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: