← previous blocknext block →recent activity
Analyzing
Block #100,849,958
12 transactions · 11 stateful · 2026-08-31 20:21:29 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,849,958 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c6f85d1…71a0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x46e2bb67…d8b3
0x34b655…2a6f
4 touches
1 conflict
0xc9d54af6…1aaf
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x513b12c7…47cd
0x34b655…2a6f
2 touches
0 conflicts
0x820d7282…6c34
0x34b655…2a6f
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 0x5c6f85d117…6371a0
Audit this contract →
← previous block·next block →recent activity