← previous blocknext block →recent activity
Analyzing
Block #100,024,572
27 transactions · 23 stateful · 2026-08-28 23:04:05 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,024,572 · 27 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
1w02w14w16w08w09w010w116w017w119w221w222w125w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x71e4ffd1…9beb
0x34b655…2a6f
6 touches
3 conflicts
0x9816fc81…4f3c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x346a0f22…ffb4
0x34b655…2a6f
6 touches
3 conflicts
0xe77c721b…7588
0x34b655…2a6f
5 touches
3 conflicts
0xf34802b3…9f10
0x1b6862…e19c
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 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity