← previous blocknext block →recent activity
Analyzing
Block #100,731,737
23 transactions · 19 stateful · 2026-08-31 10:26:22 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,731,737 · 23 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
2w03w14w26w07w18w210w311w012w115w218w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce519857…e5c4
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
0x34b655…2a6f
4 touches
1 conflict
0x980c7865…00a7
0x34b655…2a6f
4 touches
1 conflict
0xa952c504…7b64
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
6 conflicts on slot 0xce51985741…24e5c4
Audit this contract →
← previous block·next block →recent activity