← previous blocknext block →recent activity
Analyzing
Block #100,628,463
30 transactions · 25 stateful · 2026-08-31 01:46:52 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,628,463 · 30 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
1w03w14w28w09w112w015w116w117w119w221w124w025w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0x76832384…dc5b
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xb20094ed…0fef
0x34b655…2a6f
4 touches
1 conflict
0xb240b520…a88a
0x34b655…2a6f
4 touches
1 conflict
0xb7e8b0c4…dec3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity