← previous blocknext block →recent activity
Analyzing
Block #101,974,635
24 transactions · 19 stateful · 2026-09-04 18:43:15 UTC
Parallelism
92/100
Blocked
5%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,974,635 · 24 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
6w010w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x7c2869d6…1203
0x34b655…2a6f
4 touches
1 conflict
0x07c2e48b…3c16
0x34b655…2a6f
3 touches
1 conflict
0x3f9f7026…a596
0x34b655…2a6f
3 touches
1 conflict
0x5a630438…0642
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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 0x261cbea79d…12e35e
Audit this contract →
← previous block·next block →recent activity