← previous blocknext block →recent activity
Analyzing
Block #100,020,688
12 transactions · 12 stateful · 2026-08-28 22:44:32 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,020,688 · 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
2w04w17w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xd48fbc4e…d61a
0x34b655…2a6f
4 touches
1 conflict
0xdb49a79a…7b89
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xf991296d…6ee5
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
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
1 conflict on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity