← previous blocknext block →recent activity
Analyzing
Block #101,892,896
13 transactions · 13 stateful · 2026-09-04 11:48:43 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,892,896 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w37w08w010w211w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04d4f30d…4dfb
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x4dffc33e…068d
0x34b655…2a6f
8 touches
6 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5746581b…0cb1
0x34b655…2a6f
6 touches
3 conflicts
0xa7e3ddfa…f0c7
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
6 conflicts on slot 0x04d4f30d9e…3b4dfb
Audit this contract →
← previous block·next block →recent activity