← previous blocknext block →recent activity
Analyzing
Block #101,067,335
22 transactions · 20 stateful · 2026-09-01 14:35:11 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,067,335 · 22 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
2w03w14w05w16w017w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x24dc9eeb…1126
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
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 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity