← previous blocknext block →recent activity
Analyzing
Block #99,849,679
15 transactions · 14 stateful · 2026-08-28 08:22:50 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,849,679 · 15 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
1w02w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0xf8926b6c…83c7
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0x02f4f6e2…47c6
0x754704…b603
4 touches
1 conflict
0x0449d018…e334
0x754704…b603
4 touches
1 conflict
0xe332b0a5…0bdb
0x754704…b603
4 touches
1 conflict
0x3b41d761…cd85
0x99c7a7…8bf0
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 0xecd87a399c…10d9c5
Audit this contract →
← previous block·next block →recent activity