← previous blocknext block →recent activity
Analyzing
Block #86,156,945
15 transactions · 14 stateful · 2026-07-07 08:32:15 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,156,945 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f9
0x34b655…2a6f
4 touches
1 conflict
0x292ded7d…7254
0x34b655…2a6f
4 touches
1 conflict
0x5bde836a…ab2c
0x34b655…2a6f
4 touches
1 conflict
0x67c64547…dfcd
0x34b655…2a6f
4 touches
1 conflict
0x73fb252e…9be9
0x34b655…2a6f
4 touches
1 conflict
0x754e4238…cdf3
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e9
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5ea
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
1 conflict on slot 0xe5bb3628b5…71e5f9
Audit this contract →
← previous block·next block →recent activity