← previous blocknext block →recent activity
Analyzing
Block #101,063,087
18 transactions · 14 stateful · 2026-09-01 14:13:40 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,063,087 · 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
2w05w16w27w29w110w211w012w113w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc15e44d2…4c3d
0x34b655…2a6f
4 touches
1 conflict
0xd0cd3305…f212
0x34b655…2a6f
4 touches
1 conflict
0xd51b3e1c…3591
0x34b655…2a6f
4 touches
1 conflict
0xdb256401…da56
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 0x89ac61bf64…6b9443
Audit this contract →
← previous block·next block →recent activity