← previous blocknext block →recent activity
Analyzing
Block #100,021,172
21 transactions · 18 stateful · 2026-08-28 22:46:58 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,021,172 · 21 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
7w010w011w112w013w114w215w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x525cb249…2e98
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x9ad82ccb…b08b
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x0c78ade3…f11a
0x34b655…2a6f
5 touches
3 conflicts
0x71fbf214…a346
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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 0x525cb249aa…d22e98
Audit this contract →
← previous block·next block →recent activity