← previous blocknext block →recent activity
Analyzing
Block #100,851,417
18 transactions · 17 stateful · 2026-08-31 20:28:49 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,851,417 · 18 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
2w04w05w16w17w29w011w314w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51cfbcbc…fa29
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0x724c319d…f409
0x34b655…2a6f
4 touches
1 conflict
0x7b35e5cd…970c
0x34b655…2a6f
4 touches
1 conflict
0x7bb8614b…46b4
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb82f494f…db33
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 0x51cfbcbcae…65fa29
Audit this contract →
← previous block·next block →recent activity