← previous blocknext block →recent activity
Analyzing
Block #99,162,092
18 transactions · 18 stateful · 2026-08-25 22:28:52 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,162,092 · 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
1w02w15w06w18w09w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0044b90d…650b
0x34b655…2a6f
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x920754e8…0ac6
0x34b655…2a6f
4 touches
1 conflict
0x9ee73309…3c09
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0xfa09be5a…1e79
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 0x0044b90d0c…97650b
Audit this contract →
← previous block·next block →recent activity