← previous blocknext block →recent activity
Analyzing
Block #102,328,439
16 transactions · 15 stateful · 2026-09-06 00:36:28 UTC
Parallelism
56/100
Blocked
40%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,328,439 · 16 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
1w04w110w211w312w413w514w015w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbbc4bdf7…c62f
0x34b655…2a6f
8 touches
6 conflicts
0x4ac4a2c2…2707
0x34b655…2a6f
8 touches
6 conflicts
0xf1e69f42…d2ec
0x34b655…2a6f
4 touches
1 conflict
0xada26538…2548
0x34b655…2a6f
4 touches
1 conflict
0xb37dfb6b…268f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity