← previous blocknext block →recent activity
Analyzing
Block #100,724,810
15 transactions · 13 stateful · 2026-08-31 09:51:32 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,724,810 · 15 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
5w010w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd2a831…bd5d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xf5ae8ab6…bbd4
0x34b655…2a6f
4 touches
1 conflict
0x7a12283f…b18a
0x34ae4d…3fc5
2 touches
0 conflicts
0xcfe06a18…b5b5
0x34ae4d…3fc5
2 touches
0 conflicts
0x76e2c80e…1811
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 0x4dd2a8311d…52bd5d
Audit this contract →
← previous block·next block →recent activity