← previous blocknext block →recent activity
Analyzing
Block #87,314,974
14 transactions · 14 stateful · 2026-07-12 17:33:31 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,314,974 · 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
6w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x974c36fe…1cd7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x122ea818…6d1a
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x3674075e…02b7
0x34b655…2a6f
2 touches
0 conflicts
0x451f5977…7300
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 0x974c36fe03…4f1cd7
Audit this contract →
← previous block·next block →recent activity