← previous blocknext block →recent activity
Analyzing
Block #100,108,545
17 transactions · 17 stateful · 2026-08-29 06:06:48 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,108,545 · 17 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc5fc032…8d7e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7d
0x34b655…2a6f
4 touches
1 conflict
0xd9d0b0b5…32f5
0x34b655…2a6f
3 touches
1 conflict
0x2bfd4dbc…63b5
0x34b655…2a6f
3 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
2 touches
0 conflicts
0x203a33b5…86c2
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 0xbc5fc032c1…c78d7e
Audit this contract →
← previous block·next block →recent activity