← previous blocknext block →recent activity
Analyzing
Block #101,663,381
17 transactions · 16 stateful · 2026-09-03 16:34:09 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,663,381 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w28w09w010w311w414w015w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x021cd478…a6d4
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x55fa157f…1c27
0x34b655…2a6f
6 touches
3 conflicts
0xf288be4f…b8bf
0x34b655…2a6f
6 touches
3 conflicts
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x021cd478ea…b9a6d4
Audit this contract →
← previous block·next block →recent activity