← previous blocknext block →recent activity
Analyzing
Block #88,160,247
16 transactions · 15 stateful · 2026-07-16 15:48:02 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,160,247 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2c1082…db16
0x34b655…2a6f
4 touches
1 conflict
0x705d8def…28b0
0x34b655…2a6f
4 touches
1 conflict
0x972273bf…d60c
0x34b655…2a6f
4 touches
1 conflict
0x9dbde438…0f64
0x34b655…2a6f
4 touches
1 conflict
0x9f4a43ea…85a0
0x34b655…2a6f
4 touches
1 conflict
0xa124184b…1dcb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2112d98…bb04
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 0xfe2c108297…2fdb16
Audit this contract →
← previous block·next block →recent activity