← previous blocknext block →recent activity
Analyzing
Block #101,661,306
15 transactions · 14 stateful · 2026-09-03 16:23:43 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,661,306 · 15 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
1w02w04w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23b2399c…6e4b
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x053a655b…6266
0x34b655…2a6f
2 touches
0 conflicts
0x14174d82…41d3
0x34b655…2a6f
2 touches
0 conflicts
0x19735267…7c01
0x34b655…2a6f
2 touches
0 conflicts
0x20558754…48ee
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 0x23b2399ccb…706e4b
Audit this contract →
← previous block·next block →recent activity