← previous blocknext block →recent activity
Analyzing
Block #87,903,151
19 transactions · 16 stateful · 2026-07-15 11:08:11 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,903,151 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w07w18w210w111w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f83113a…dcd8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x30f3ece3…c237
0x34b655…2a6f
4 touches
1 conflict
0x3f4d9d89…7299
0x34b655…2a6f
4 touches
1 conflict
0x59e84008…7fac
0x34b655…2a6f
4 touches
1 conflict
0x59e84008…7fad
0x34b655…2a6f
4 touches
1 conflict
0x6d156df4…b643
0x34b655…2a6f
4 touches
1 conflict
0x6d156df4…b644
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
3 conflicts on slot 0x9f83113ae0…0edcd8
Audit this contract →
← previous block·next block →recent activity