← previous blocknext block →recent activity
Analyzing
Block #88,074,604
14 transactions · 13 stateful · 2026-07-16 06:14:55 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,074,604 · 14 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
1w02w16w09w010w111w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffcb5f20…df5a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x05781a85…664f
0x34b655…2a6f
4 touches
1 conflict
0x0b05d77e…6f90
0x34b655…2a6f
4 touches
1 conflict
0x1bb56de3…732e
0x34b655…2a6f
4 touches
1 conflict
0x35bd6a25…9de5
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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 0xffcb5f205c…83df5a
Audit this contract →
← previous block·next block →recent activity