← previous blocknext block →recent activity
Analyzing
Block #107,849,417
28 transactions · 26 stateful · 2026-09-25 08:48:56 UTC
Parallelism
50/100
Blocked
69%
Avg conflicts / tx
1.93
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #107,849,417 · 28 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w39w410w511w612w713w815w1016w1117w1218w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b76a1fb…fdfc
0x34b655…2a6f
14 touches
21 conflicts
0x01e6c943…e1fb
0x34b655…2a6f
14 touches
21 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xfa9926f9…570a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf75c3a6b…0568
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x2b76a1fb53…5afdfc
Audit this contract →
← previous block·next block →recent activity