← previous blocknext block →recent activity
Analyzing
Block #105,633,479
17 transactions · 17 stateful · 2026-09-17 14:49:53 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,633,479 · 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
2w03w17w08w111w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfae4e22b…bc46
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x30e75e4f…291b
0x34b655…2a6f
4 touches
1 conflict
0x3139f1c1…2715
0xa9da3c…540f
2 touches
1 conflict
0x23501896…00dd
0x3bd359…433a
2 touches
0 conflicts
0x00000000…000a
0x3d80f5…41b3
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity