← previous blocknext block →recent activity
Analyzing
Block #101,986,622
33 transactions · 23 stateful · 2026-09-04 19:44:04 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,986,622 · 33 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
2w09w013w117w118w221w222w323w326w429w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xaa5de1…d330
6 touches
3 conflicts
0x00000000…0003
0xaa5de1…d330
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xbcc1b459…f94f
0x3bd359…433a
6 touches
3 conflicts
0xa74cd79c…705a
0x405b63…7777
6 touches
3 conflicts
0x00000000…0000
0xaa5de1…d330
6 touches
3 conflicts
0x8fecada7…ac93
0xd32edf…ff58
5 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity