← previous blocknext block →recent activity
Analyzing
Block #100,732,293
18 transactions · 18 stateful · 2026-08-31 10:29:10 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,732,293 · 18 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
2w05w06w08w111w012w013w214w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0xa952c504…7b64
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
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 0x414698942a…665990
Audit this contract →
← previous block·next block →recent activity