← previous blocknext block →recent activity
Analyzing
Block #104,983,411
18 transactions · 16 stateful · 2026-09-15 08:17:58 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,983,411 · 18 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
2w04w05w18w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe580c096…2260
0x34b655…2a6f
4 touches
1 conflict
0xe9c34303…7f10
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x2ff49a15…2bb3
0x34b655…2a6f
2 touches
0 conflicts
0x58e8bb59…8306
0x34b655…2a6f
2 touches
0 conflicts
0x6c7c1a4b…5751
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 0xbaf77397f3…58e798
Audit this contract →
← previous block·next block →recent activity