← previous blocknext block →recent activity
Analyzing
Block #100,863,245
15 transactions · 12 stateful · 2026-08-31 21:28:19 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,863,245 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5bb3043…085a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0xb71f7e11…d40e
0x34ae4d…3fc5
2 touches
0 conflicts
0xdeed550b…338b
0x34ae4d…3fc5
2 touches
0 conflicts
0xe49b1b9b…0be1
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
1 conflict on slot 0xf5bb304334…65085a
Audit this contract →
← previous block·next block →recent activity