← previous blocknext block →recent activity
Analyzing
Block #107,443,929
16 transactions · 15 stateful · 2026-09-23 22:45:57 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,443,929 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w28w010w111w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2438e6d…3c20
0x34b655…2a6f
6 touches
3 conflicts
0x3da6ec2b…b836
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1af
0x37db7f…ec7b
6 touches
3 conflicts
0x662d9b98…0f6b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
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
3 conflicts on slot 0xd2438e6d64…3d3c20
Audit this contract →
← previous block·next block →recent activity