← previous blocknext block →recent activity
Analyzing
Block #87,671,194
17 transactions · 15 stateful · 2026-07-14 09:16:21 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,671,194 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w09w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a2678e…64da
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8b99f3b2…5d84
0x34b655…2a6f
4 touches
1 conflict
0x8b99f3b2…5d85
0x34b655…2a6f
4 touches
1 conflict
0xa0acdcf7…bd86
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd97c2fdb…27d5
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 0x16a2678e7a…ce64da
Audit this contract →
← previous block·next block →recent activity