← previous blocknext block →recent activity
Analyzing
Block #100,853,201
9 transactions · 7 stateful · 2026-08-31 20:37:48 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,853,201 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5be73264…4d9c
0x34b655…2a6f
4 touches
1 conflict
0xbe88cfca…0bf1
0x34b655…2a6f
4 touches
1 conflict
0xe8587278…40f5
0x34b655…2a6f
4 touches
1 conflict
0xec653969…3e38
0x34b655…2a6f
4 touches
1 conflict
0xec653969…3e39
0x34b655…2a6f
4 touches
1 conflict
0xf1ff9f76…9442
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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 0x5be7326471…814d9c
Audit this contract →
← previous block·next block →recent activity