Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a0476a7d1220212798d052a83cfec8b0f9551bf4dee7d005e1eb3cfcac2cbd

Tx prefix hash: 1e3c58d973d12b46c70007d64284ccf3ab8732b27c994d8049a3e5dab45f2e11
Tx public key: ec462ff5458d38b4a8406fb964f0e5b09c3ebeeb7e521ee3272288f3a0cb33ef
Timestamp: 1771657163 Timestamp [UTC]: 2026-02-21 06:59:23 Age [y:d:h:m:s]: 00:058:07:46:53
Block: 1482465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33968 RingCT/type: yes/0
Extra: 01ec462ff5458d38b4a8406fb964f0e5b09c3ebeeb7e521ee3272288f3a0cb33ef021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d3d2f055f0423666c8ad89a1ae0ef662150200e9828f3c22c3869971f8ec6088 0.000600000000 1971857 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": 1482475, "vin": [ { "gen": { "height": 1482465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3d2f055f0423666c8ad89a1ae0ef662150200e9828f3c22c3869971f8ec6088" } } ], "extra": [ 1, 236, 70, 47, 245, 69, 141, 56, 180, 168, 64, 111, 185, 100, 240, 229, 176, 156, 62, 190, 235, 126, 82, 30, 227, 39, 34, 136, 243, 160, 203, 51, 239, 2, 17, 0, 0, 0, 2, 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: