Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f87fb0bb923aeef0016e07efe3a9edd34e5f1441556a06da89f27bb5947b84

Tx prefix hash: 18b0f9eea6e3294ba6b20abe24c1d0fe7d45fef4f8990adbc2d280286dd6feab
Tx public key: 912e7bef5ceb9616807f0ea2077408f1e0cf220cb5f1496a021ca35f2ea7e4a5
Timestamp: 1772115618 Timestamp [UTC]: 2026-02-26 14:20:18 Age [y:d:h:m:s]: 00:266:22:01:12
Block: 1486246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196430 RingCT/type: yes/0
Extra: 01912e7bef5ceb9616807f0ea2077408f1e0cf220cb5f1496a021ca35f2ea7e4a5021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8db6da2f1a7ed3637d50127d5251ec7f6a2e39811ee2de2664f2a75f1b53151 0.000600000000 1975696 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": 1486256, "vin": [ { "gen": { "height": 1486246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8db6da2f1a7ed3637d50127d5251ec7f6a2e39811ee2de2664f2a75f1b53151" } } ], "extra": [ 1, 145, 46, 123, 239, 92, 235, 150, 22, 128, 127, 14, 162, 7, 116, 8, 241, 224, 207, 34, 12, 181, 241, 73, 106, 2, 28, 163, 95, 46, 167, 228, 165, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: