← previous blocknext block →recent activity
Analyzing
Block #100,612,751
22 transactions · 20 stateful · 2026-08-31 00:27:50 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,612,751 · 22 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
1w02w03w14w05w18w09w010w113w014w115w119w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xc693f151…3ed9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcf37f77e…a027
0x34b655…2a6f
4 touches
1 conflict
0xe2de1aea…8024
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity