← previous blocknext block →recent activity
Analyzing
Block #107,813,137
28 transactions · 27 stateful · 2026-09-25 05:46:20 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,137 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w08w111w212w114w015w116w117w218w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xa0cbbfcc…3133
0x34b655…2a6f
8 touches
6 conflicts
0x2b76a1fb…fdfc
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x961c0cd9…0937
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x01e6c943…e1fb
0x34b655…2a6f
8 touches
6 conflicts
0xd1448207…452d
0x34b655…2a6f
8 touches
6 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: Perpl
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity