← previous blocknext block →recent activity
Analyzing
Block #101,307,036
21 transactions · 19 stateful · 2026-09-02 10:41:16 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,307,036 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w27w38w49w511w612w215w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x05732507…d5bf
0x34b655…2a6f
4 touches
1 conflict
0x094e3c9c…ec00
0x34b655…2a6f
4 touches
1 conflict
0x2d02f869…1f83
0x34b655…2a6f
4 touches
1 conflict
0x2da105e9…59b0
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity