← previous blocknext block →recent activity
Analyzing
Block #101,974,299
18 transactions · 18 stateful · 2026-09-04 18:41:32 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,974,299 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w17w29w310w011w112w313w415w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb1b66a1…ce4e
0x34b655…2a6f
6 touches
3 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xcc8b6d32…6601
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe65e9a26…a0b5
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
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
3 conflicts on slot 0xeb1b66a1ed…55ce4e
Audit this contract →
← previous block·next block →recent activity