Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36c80c7eb57138babfa1eca287c3c5cabbfe6e439d5177a6a04bf51d6c77b4b

Tx prefix hash: 2668672c2cda851c540b85cfbb8473c0782a6fe32f3b73d1a8bce488c6d83234
Tx public key: 369c990fd80d632624a1e4938f5e28800fa79b4cefefef175df9396f94f80296
Timestamp: 1771490618 Timestamp [UTC]: 2026-02-19 08:43:38 Age [y:d:h:m:s]: 00:269:01:51:44
Block: 1481091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197742 RingCT/type: yes/0
Extra: 01369c990fd80d632624a1e4938f5e28800fa79b4cefefef175df9396f94f80296021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa8ad8935cc1d880e1fc09df258029b20210491a1295f5796ffd9ccfd6c235a2 0.000600000000 1970467 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": 1481101, "vin": [ { "gen": { "height": 1481091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa8ad8935cc1d880e1fc09df258029b20210491a1295f5796ffd9ccfd6c235a2" } } ], "extra": [ 1, 54, 156, 153, 15, 216, 13, 99, 38, 36, 161, 228, 147, 143, 94, 40, 128, 15, 167, 155, 76, 239, 239, 239, 23, 93, 249, 57, 111, 148, 248, 2, 150, 2, 17, 0, 0, 0, 2, 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: