← previous blocknext block →recent activity
Analyzing
Block #99,625,415
18 transactions · 16 stateful · 2026-08-27 13:27:59 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,625,415 · 18 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
1w02w03w16w08w09w111w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed903df2…6ea4
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x676052f0…a5f6
0x34b655…2a6f
4 touches
1 conflict
0x72ad142e…61a3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xed903df2a7…046ea4
Audit this contract →
← previous block·next block →recent activity