← previous blocknext block →recent activity
Analyzing
Block #104,878,065
18 transactions · 18 stateful · 2026-09-14 23:27:52 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,878,065 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w311w414w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x358633c5…2b29
0x34b655…2a6f
4 touches
1 conflict
0x41f69129…1c71
0x34b655…2a6f
4 touches
1 conflict
0x5d3436c8…7ce0
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity