← previous blocknext block →recent activity
Analyzing
Block #105,636,531
28 transactions · 21 stateful · 2026-09-17 15:05:14 UTC
Parallelism
93/100
Blocked
29%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,636,531 · 28 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
4w08w09w112w013w114w118w019w121w022w125w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5024e912…ce7c
0x34b655…2a6f
4 touches
1 conflict
0x858fb0e5…54c9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd1448207…452d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0x5024e912b2…97ce7c
Audit this contract →
← previous block·next block →recent activity