← previous blocknext block →recent activity
Analyzing
Block #100,876,737
13 transactions · 10 stateful · 2026-08-31 22:36:10 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,876,737 · 13 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
1w03w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0x5ddd9edb…6ce7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x06ce5d4b…c122
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9285
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9289
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
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 0xf984d8ab41…c96e4f
Audit this contract →
← previous block·next block →recent activity