← previous blocknext block →recent activity
Analyzing
Block #100,732,625
15 transactions · 14 stateful · 2026-08-31 10:30:50 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,732,625 · 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
2w03w17w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa952c504…7b64
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x02f4f6e2…47c6
0x754704…b603
4 touches
1 conflict
0x0449d018…e334
0x754704…b603
4 touches
1 conflict
0xe332b0a5…0bdb
0x754704…b603
4 touches
1 conflict
0x3b41d761…cd85
0x99c7a7…8bf0
4 touches
1 conflict
0xe10ff4f0…94b7
0x99c7a7…8bf0
4 touches
1 conflict
0x77e548f6…7a30
0x34b655…2a6f
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 0xa952c50488…287b64
Audit this contract →
← previous block·next block →recent activity