← previous blocknext block →recent activity
Analyzing
Block #100,609,678
10 transactions · 9 stateful · 2026-08-31 00:12:23 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,609,678 · 10 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
2w03w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2263bea…6aa2
0x2b46c0…1669
4 touches
1 conflict
0xeba56708…8cd7
0x2b46c0…1669
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf1a14809…56fd
0x2b46c0…1669
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa0a8ac53…199c
0xa6afd3…d132
4 touches
1 conflict
0x5778d110…d2e6
0xc8689a…ee79
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: 0x2b46c08c…ec1669
1 conflict on slot 0xe2263beaa4…316aa2
Audit this contract →
← previous block·next block →recent activity