← previous blocknext block →recent activity
Analyzing
Block #102,817,696
27 transactions · 26 stateful · 2026-09-07 17:52:09 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,817,696 · 27 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
1w02w13w04w05w16w211w012w113w214w117w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x650a2cf3…72bf
0x34b655…2a6f
8 touches
6 conflicts
0x044844a0…7418
0x34b655…2a6f
6 touches
3 conflicts
0x0d03bddb…6658
0x34b655…2a6f
6 touches
3 conflicts
0x73bc80c5…5720
0xd32edf…ff58
5 touches
3 conflicts
0x394c3833…b4aa
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity