← previous blocknext block →recent activity
Analyzing
Block #98,425,135
17 transactions · 13 stateful · 2026-08-23 07:57:54 UTC
Parallelism
82/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,425,135 · 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
2w07w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f00a5b3…bf76
0x34b655…2a6f
4 touches
1 conflict
0x2aae7326…8b66
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58799a46…7030
0x34b655…2a6f
4 touches
1 conflict
0x598992a9…5aa2
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
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 0x1f00a5b37a…aebf76
Audit this contract →
← previous block·next block →recent activity