← previous blocknext block →recent activity
Analyzing
Block #101,852,493
16 transactions · 13 stateful · 2026-09-04 08:25:22 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,852,493 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0677157c…b5dc
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x0fb297a7…d8f7
0x34b655…2a6f
4 touches
1 conflict
0x1bfa6712…9044
0x34b655…2a6f
4 touches
1 conflict
0x253b3d88…fdc2
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x2ffc0025…191b
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
1 conflict on slot 0x0677157c1f…b6b5dc
Audit this contract →
← previous block·next block →recent activity