← previous blocknext block →recent activity
Analyzing
Block #106,186,153
20 transactions · 17 stateful · 2026-09-19 13:13:54 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,186,153 · 20 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
4w05w111w013w014w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x252bfe4b…d41d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x06ce5d4b…c122
0x34ae4d…3fc5
2 touches
0 conflicts
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x46279ae7…20dd
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity