← previous blocknext block →recent activity
Analyzing
Block #100,701,135
18 transactions · 13 stateful · 2026-08-31 07:52:25 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,701,135 · 18 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
16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0001
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0005
0x354d92…66fb
2 touches
0 conflicts
0x38b5b2ce…c5bb
0x354d92…66fb
2 touches
0 conflicts
0x8a2f9a36…fb4a
0x354d92…66fb
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