← previous blocknext block →recent activity
Analyzing
Block #101,968,373
26 transactions · 24 stateful · 2026-09-04 18:11:31 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,968,373 · 26 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
3w04w08w09w112w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bf5f17…1bb1
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x45e0cbdf…e991
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x4ab70ccd…2683
0x34b655…2a6f
2 touches
0 conflicts
0x5746581b…0cb1
0x34b655…2a6f
2 touches
0 conflicts
0x665b15b4…320f
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 0x34bf5f1727…481bb1
Audit this contract →
← previous block·next block →recent activity