← previous blocknext block →recent activity
Analyzing
Block #100,022,078
19 transactions · 19 stateful · 2026-08-28 22:51:31 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,022,078 · 19 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
1w04w07w19w010w113w215w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65b5c7f0…57ef
0x34b655…2a6f
6 touches
3 conflicts
0xa0998a89…1f5a
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc012582c…f37d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x49890ced…6f23
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 0x65b5c7f077…9f57ef
Audit this contract →
← previous block·next block →recent activity