← previous blocknext block →recent activity
Analyzing
Block #100,627,663
24 transactions · 23 stateful · 2026-08-31 01:42:51 UTC
Parallelism
92/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,627,663 · 24 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
3w07w012w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00500a94…20d5
0x34b655…2a6f
4 touches
1 conflict
0xb0449597…3679
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x6284ed3e…6180
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x00500a94bf…5a20d5
Audit this contract →
← previous block·next block →recent activity