← previous blocknext block →recent activity
Analyzing
Block #105,851,137
15 transactions · 14 stateful · 2026-09-18 09:06:47 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,851,137 · 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
2w03w14w05w17w08w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdecb9ef3…51c5
0x34b655…2a6f
4 touches
1 conflict
0xe53bd661…5352
0x34b655…2a6f
4 touches
1 conflict
0xf8a78bc6…2a1f
0x34b655…2a6f
4 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x2c001e45…d749
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x987859be…2686
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 0xdecb9ef317…6151c5
Audit this contract →
← previous block·next block →recent activity