← previous blocknext block →recent activity
Analyzing
Block #100,620,912
20 transactions · 20 stateful · 2026-08-31 01:08:53 UTC
Parallelism
90/100
Blocked
10%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,620,912 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcaa5e459…c7eb
0x34b655…2a6f
4 touches
1 conflict
0xf98c943e…7c44
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
2 touches
0 conflicts
0x3faf81e5…1892
0x34b655…2a6f
2 touches
0 conflicts
0x40928f94…a274
0x34b655…2a6f
2 touches
0 conflicts
0x5273be82…485e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity