← previous blocknext block →recent activity
Analyzing
Block #101,016,220
19 transactions · 16 stateful · 2026-09-01 10:17:52 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,016,220 · 19 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
1w03w04w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xead15497…1dbe
0x34b655…2a6f
4 touches
1 conflict
0x0d85683a…ecd8
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0xb0a8e01c…d86c
0x34b655…2a6f
4 touches
1 conflict
0xea07f200…7f8c
0x065c9d…c394
3 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
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 0xead15497a3…971dbe
Audit this contract →
← previous block·next block →recent activity