← previous blocknext block →recent activity
Analyzing
Block #100,633,104
30 transactions · 23 stateful · 2026-08-31 02:10:13 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,633,104 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w213w314w417w018w122w223w228w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee90529a…abb1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
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 0xee90529a00…33abb1
Audit this contract →
← previous block·next block →recent activity