← previous blocknext block →recent activity
Analyzing
Block #104,877,112
14 transactions · 14 stateful · 2026-09-14 23:23:04 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,877,112 · 14 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
2w03w15w06w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0x8b8be7bd…7f73
0x34b655…2a6f
4 touches
1 conflict
0x0c5747f0…710b
0x34b655…2a6f
4 touches
1 conflict
0x382434ca…96b5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x48a0f121…953b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x711ceb8da2…d35202
Audit this contract →
← previous block·next block →recent activity