← previous blocknext block →recent activity
Analyzing
Block #101,992,182
19 transactions · 19 stateful · 2026-09-04 20:12:20 UTC
Parallelism
63/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,992,182 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w39w311w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x102ab3ca…83b4
0x34b655…2a6f
8 touches
6 conflicts
0xa963f2ee…ff57
0x34b655…2a6f
8 touches
6 conflicts
0x8849e72f…b522
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd07b013b…90cb
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
0x34b655…2a6f
6 touches
3 conflicts
0xee46716c…d788
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 0x102ab3ca0d…2883b4
Audit this contract →
← previous block·next block →recent activity