← previous blocknext block →recent activity
Analyzing
Block #100,848,415
18 transactions · 14 stateful · 2026-08-31 20:13:43 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,848,415 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32b2548c…4105
0x34b655…2a6f
6 touches
3 conflicts
0x6b6f1023…d6b5
0x34b655…2a6f
4 touches
1 conflict
0x7329b760…75eb
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x9c7c84be…2cab
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
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
3 conflicts on slot 0x32b2548c34…2f4105
Audit this contract →
← previous block·next block →recent activity