← previous blocknext block →recent activity
Analyzing
Block #99,250,162
17 transactions · 12 stateful · 2026-08-26 05:51:57 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,250,162 · 17 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
3w010w111w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68dfc6ca…56ac
0x34b655…2a6f
4 touches
1 conflict
0x059e0ac0…0267
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x387a2497…49e1
0x34b655…2a6f
2 touches
0 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
2 touches
0 conflicts
0x535fd3c8…ba9e
0x34b655…2a6f
2 touches
0 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
2 touches
0 conflicts
0x6cc0470a…7dc0
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 0x68dfc6ca63…a056ac
Audit this contract →
← previous block·next block →recent activity