← previous blocknext block →recent activity
Analyzing
Block #105,583,893
13 transactions · 12 stateful · 2026-09-17 10:40:14 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,583,893 · 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ecb9366…f4f2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x62811193…1868
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186c
0x34ae4d…3fc5
2 touches
0 conflicts
0xd671bc34…553c
0x34ae4d…3fc5
2 touches
0 conflicts
0xd8fd2add…50fc
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 0x3ecb93668a…3df4f2
Audit this contract →
← previous block·next block →recent activity