← previous blocknext block →recent activity
Analyzing
Block #107,823,281
28 transactions · 27 stateful · 2026-09-25 06:37:24 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,281 · 28 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
2w03w14w08w29w110w211w113w114w215w316w217w318w419w527w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ba83b5…d0a8
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x370bbcfb…5d6c
0xd32edf…ff58
7 touches
6 conflicts
0x2b856d86…7988
0x34b655…2a6f
6 touches
3 conflicts
0x6913fc36…ae5d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xa7ba83b5e1…e4d0a8
Audit this contract →
← previous block·next block →recent activity