← previous blocknext block →recent activity
Analyzing
Block #104,023,936
7 transactions · 7 stateful · 2026-09-11 23:16:12 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,023,936 · 7 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
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb575cf74…fbd5
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00e84dca…18f9
0x34b655…2a6f
2 touches
0 conflicts
0x185eacc9…9e18
0x34b655…2a6f
2 touches
0 conflicts
0x24020994…8b01
0x34b655…2a6f
2 touches
0 conflicts
0x26ee1da7…3c2a
0x34b655…2a6f
2 touches
0 conflicts
0x6324ccc9…14fd
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity