← previous blocknext block →recent activity
Analyzing
Block #106,544,453
13 transactions · 13 stateful · 2026-09-20 19:17:14 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,544,453 · 13 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
1w02w17w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd911522b…e960
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x735a86cd…b64d
0x34b655…2a6f
4 touches
1 conflict
0x82395399…0c17
0x34b655…2a6f
4 touches
1 conflict
0xace6677d…659d
0x34b655…2a6f
4 touches
1 conflict
0x3ba7edbb…80e6
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 0xd911522b07…20e960
Audit this contract →
← previous block·next block →recent activity