Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc39741c4dbb4573e2fc4a21b5764e722a0c5c24c60d2e6ecd9a2bff1952b4c3

Tx prefix hash: bff4bac3e79db3b572c7a52fa615c63c9b5620d79f7138f4eab26f5b5f49ac97
Tx public key: 028b810b2adbfba4679223d93781c93eeec68ff3e91e73f6c76ca812fbc14882
Timestamp: 1774546121 Timestamp [UTC]: 2026-03-26 17:28:41 Age [y:d:h:m:s]: 00:234:20:48:58
Block: 1506369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173324 RingCT/type: yes/0
Extra: 01028b810b2adbfba4679223d93781c93eeec68ff3e91e73f6c76ca812fbc14882021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9eaa60a9b4fe20dbbe46b14cde6f90a42b661b043088e3b85ae3047419f650a9 0.000600000000 1996113 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": 1506379, "vin": [ { "gen": { "height": 1506369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eaa60a9b4fe20dbbe46b14cde6f90a42b661b043088e3b85ae3047419f650a9" } } ], "extra": [ 1, 2, 139, 129, 11, 42, 219, 251, 164, 103, 146, 35, 217, 55, 129, 201, 62, 238, 198, 143, 243, 233, 30, 115, 246, 199, 108, 168, 18, 251, 193, 72, 130, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: