← previous blocknext block →recent activity
Analyzing
Block #100,864,721
29 transactions · 20 stateful · 2026-08-31 21:35:44 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,864,721 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w116w017w018w119w020w125w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xe61a3df2…f763
0x34b655…2a6f
6 touches
3 conflicts
0x6eff310a…c34c
0x34ae4d…3fc5
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
4 touches
1 conflict
0xe49b1b9b…0be1
0x34ae4d…3fc5
4 touches
1 conflict
0x295780b7…d2d1
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity