← previous blocknext block →recent activity
Analyzing
Block #104,195,798
18 transactions · 16 stateful · 2026-09-12 13:50:04 UTC
Parallelism
61/100
Blocked
38%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,195,798 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w412w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
10 touches
10 conflicts
0x9ddfd674…2a54
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa652b48e…f543
0x34b655…2a6f
6 touches
3 conflicts
0x6d1dd980…6117
0x34b655…2a6f
6 touches
3 conflicts
0x7ac265cd…0253
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
10 conflicts on slot 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity