← previous blocknext block →recent activity
Analyzing
Block #100,021,212
15 transactions · 14 stateful · 2026-08-28 22:47:10 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,021,212 · 15 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
1w02w14w27w011w312w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5c5d72…914b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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 0x6d5c5d726f…33914b
Audit this contract →
← previous block·next block →recent activity