← previous blocknext block →recent activity
Analyzing
Block #100,627,812
28 transactions · 26 stateful · 2026-08-31 01:43:36 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,627,812 · 28 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
2w03w04w06w17w18w210w314w318w319w422w124w426w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe73a5eb9…5d49
0x34b655…2a6f
10 touches
10 conflicts
0xb482658a…e4f5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x044844a0…7418
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xa169711f…c7f3
0x34b655…2a6f
6 touches
3 conflicts
0x9513aafb…bb7f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
10 conflicts on slot 0xe73a5eb9f5…fd5d49
Audit this contract →
← previous block·next block →recent activity