← previous blocknext block →recent activity
Analyzing
Block #84,193,818
10 transactions · 9 stateful · 2026-06-28 06:24:50 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,193,818 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x8be49b48…0005
0x1001ff…1001
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0x00000000…0000
0x276664…5732
2 touches
0 conflicts
0x00000000…0002
0x276664…5732
2 touches
0 conflicts
0x00000000…0004
0x276664…5732
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xe75cebb6e9…636b36
Audit this contract →
← previous block·next block →recent activity