Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64ec13352c8d314b1af6d2a2cb52eb0feeef4114f7d4b9ed6edb4cdaf1e39a95

Tx prefix hash: 003153370b7641d4f0eb7fe016c426831e54f645c22a72b9daeed2a4df8650da
Tx public key: fe8fd565340b6db01ff99ab8dca40575983646943f8eb1d8d69b09cc4a2d5e86
Timestamp: 1742317978 Timestamp [UTC]: 2025-03-18 17:12:58 Age [y:d:h:m:s]: 01:167:23:50:05
Block: 1242119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384580 RingCT/type: yes/0
Extra: 01fe8fd565340b6db01ff99ab8dca40575983646943f8eb1d8d69b09cc4a2d5e860211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1b5ddcf9c93b8538859b94e1aea9b9b6aaa510324ae734d96f798f3402fb7a95 0.000600000000 1729092 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": 1242129, "vin": [ { "gen": { "height": 1242119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b5ddcf9c93b8538859b94e1aea9b9b6aaa510324ae734d96f798f3402fb7a95" } } ], "extra": [ 1, 254, 143, 213, 101, 52, 11, 109, 176, 31, 249, 154, 184, 220, 164, 5, 117, 152, 54, 70, 148, 63, 142, 177, 216, 214, 155, 9, 204, 74, 45, 94, 134, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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: