← previous blocknext block →recent activity
Analyzing
Block #105,434,643
19 transactions · 18 stateful · 2026-09-16 22:09:08 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,434,643 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w08w111w016w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a76e0e…6ee2
0x34b655…2a6f
4 touches
1 conflict
0x157b7af2…12fa
0x34b655…2a6f
4 touches
1 conflict
0x1d69cd40…3a60
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e5
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0x05a76e0e55…296ee2
Audit this contract →
← previous block·next block →recent activity