← previous blocknext block →recent activity
Analyzing
Block #86,948,631
12 transactions · 11 stateful · 2026-07-11 00:44:23 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,948,631 · 12 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a6982a4…158c
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0xded7831c…3c4a
0x34b655…2a6f
4 touches
1 conflict
0xd1ec0dfd…ccc0
0xc8689a…ee79
4 touches
1 conflict
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0x24de48ed…b934
0x34b655…2a6f
2 touches
0 conflicts
0x74fce6ad…7895
0x34b655…2a6f
2 touches
0 conflicts
0x890eac6e…1c0d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x4a6982a445…f8158c
Audit this contract →
← previous block·next block →recent activity