← previous blocknext block →recent activity
Analyzing
Block #86,737,136
23 transactions · 18 stateful · 2026-07-10 01:10:48 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,737,136 · 23 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
5w06w17w29w314w315w416w018w520w021w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x8e9aaa9b…c434
0x34b655…2a6f
6 touches
3 conflicts
0xff9e45bf…99a0
0x34b655…2a6f
6 touches
3 conflicts
0x546671c8…080a
0x34b655…2a6f
4 touches
1 conflict
0x55125205…f0ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity