Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842e7b63284fcf4c0f641d60dcbdf01736eb2faafeb08db28b6747f1f334b1e0

Tx prefix hash: a38845d33b1b1140df1eb68c43209f443d1e769b63a3a18d9667e0634f04e814
Tx public key: 4bedeebee79080a6405d8c972cb32a3f5c5579b70f4f94c6a29ca1ae55d1a20b
Timestamp: 1730864601 Timestamp [UTC]: 2024-11-06 03:43:21 Age [y:d:h:m:s]: 02:008:13:25:02
Block: 1147536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530750 RingCT/type: yes/0
Extra: 014bedeebee79080a6405d8c972cb32a3f5c5579b70f4f94c6a29ca1ae55d1a20b021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3c7321f5aa3b11813268e4e8679c79188ccc83f61d7381e370eb2619ff3dbb2b 0.000600000000 1632235 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": 1147546, "vin": [ { "gen": { "height": 1147536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c7321f5aa3b11813268e4e8679c79188ccc83f61d7381e370eb2619ff3dbb2b" } } ], "extra": [ 1, 75, 237, 238, 190, 231, 144, 128, 166, 64, 93, 140, 151, 44, 179, 42, 63, 92, 85, 121, 183, 15, 79, 148, 198, 162, 156, 161, 174, 85, 209, 162, 11, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: