← previous blocknext block →recent activity
Analyzing
Block #100,562,058
29 transactions · 24 stateful · 2026-08-30 20:12:49 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.34
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,562,058 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w28w09w011w015w118w119w124w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733c7779…a647
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
4 touches
1 conflict
0x10d80fee…dbda
0x2b46c0…1669
4 touches
1 conflict
0x2f4b2cf9…4e1e
0x2b46c0…1669
4 touches
1 conflict
0x595839b9…ca61
0x2b46c0…1669
4 touches
1 conflict
0x5cc231f5…f1cd
0x2b46c0…1669
4 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
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 0x733c7779fd…f4a647
Audit this contract →
← previous block·next block →recent activity