← previous blocknext block →recent activity
Analyzing
Block #102,871,118
21 transactions · 21 stateful · 2026-09-07 22:20:59 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,871,118 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w413w014w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3ac42d3…831b
0x34b655…2a6f
12 touches
15 conflicts
0x68dfc6ca…56ac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x8a8af67b…1bdd
0x34b655…2a6f
6 touches
3 conflicts
0x2d6af7d3…5e30
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x24ed74ea…a3ff
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
15 conflicts on slot 0xe3ac42d3e2…82831b
Audit this contract →
← previous block·next block →recent activity