← previous blocknext block →recent activity
Analyzing
Block #101,016,543
18 transactions · 15 stateful · 2026-09-01 10:19:30 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,016,543 · 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
8w016w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa771fb55…48d2
0x34b655…2a6f
4 touches
1 conflict
0xb2e9ab60…6e48
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x286711a5…b3bf
0x34b655…2a6f
2 touches
0 conflicts
0x3e1b21c6…b1e4
0x34b655…2a6f
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 0xa771fb55cb…0a48d2
Audit this contract →
← previous block·next block →recent activity