← previous blocknext block →recent activity
Analyzing
Block #99,211,787
16 transactions · 12 stateful · 2026-08-26 02:38:52 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,211,787 · 16 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
6w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad4e90b…33a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x01d6b619…6084
0x34b655…2a6f
2 touches
0 conflicts
0x0fd5f9da…1e9b
0x34b655…2a6f
2 touches
0 conflicts
0x126c10ea…a328
0x34b655…2a6f
2 touches
0 conflicts
0x3bb07d5e…582e
0x34b655…2a6f
2 touches
0 conflicts
0x3e49348b…9445
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 0xbad4e90ba6…2233a5
Audit this contract →
← previous block·next block →recent activity