← previous blocknext block →recent activity
Analyzing
Block #100,873,646
15 transactions · 15 stateful · 2026-08-31 22:20:38 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,873,646 · 15 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
1w03w14w05w16w27w112w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xebcd724a…8de4
0x34b655…2a6f
4 touches
1 conflict
0xf4257ede…1968
0x065c9d…c394
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
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
3 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity