← previous blocknext block →recent activity
Analyzing
Block #101,987,902
22 transactions · 19 stateful · 2026-09-04 19:50:34 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,987,902 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w18w19w215w016w118w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf199a64…16ed
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x65c77c28…1a54
0x34b655…2a6f
6 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x421711fb…15e2
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
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 0xaf199a6445…a316ed
Audit this contract →
← previous block·next block →recent activity