← previous blocknext block →recent activity
Analyzing
Block #101,798,115
13 transactions · 13 stateful · 2026-09-04 03:51:51 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,798,115 · 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
1w04w15w06w17w29w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x4089d428…b018
0x34b655…2a6f
2 touches
0 conflicts
0x6412fc4f…596f
0x34b655…2a6f
2 touches
0 conflicts
0x7b3c201f…283b
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
6 conflicts on slot 0x4ee0b65a93…c56d40
Audit this contract →
← previous block·next block →recent activity