← previous blocknext block →recent activity
Analyzing
Block #104,325,988
16 transactions · 16 stateful · 2026-09-13 00:50:38 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,325,988 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w18w39w412w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x141def99…ea38
0x34b655…2a6f
12 touches
15 conflicts
0x14cc77c7…69c4
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xe8843e0b…90af
0x34b655…2a6f
6 touches
3 conflicts
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x141def99a2…8cea38
Audit this contract →
← previous block·next block →recent activity