← previous blocknext block →recent activity
Analyzing
Block #100,611,073
31 transactions · 23 stateful · 2026-08-31 00:19:24 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,611,073 · 31 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
2w04w05w16w015w116w117w219w321w023w124w125w226w027w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7be178f…2fb2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0161566e…abb2
0xa6afd3…d132
6 touches
3 conflicts
0xc45e4fb5…7cc3
0xa6afd3…d132
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9486cd4f…2ed2
0x34b655…2a6f
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 0xd7be178f26…dc2fb2
Audit this contract →
← previous block·next block →recent activity