← previous blocknext block →recent activity
Analyzing
Block #104,202,233
19 transactions · 16 stateful · 2026-09-12 14:22:48 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,202,233 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w110w211w312w413w514w618w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ccb0b…5139
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xcd1306ad…f1b8
0x34b655…2a6f
8 touches
6 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
6 touches
3 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
6 touches
3 conflicts
0x7ef4ba09…2a25
0x34b655…2a6f
4 touches
1 conflict
0x8d1a981c…a066
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
21 conflicts on slot 0xb33ccb0b91…3b5139
Audit this contract →
← previous block·next block →recent activity