← previous blocknext block →recent activity
Analyzing
Block #104,194,454
23 transactions · 17 stateful · 2026-09-12 13:43:16 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,194,454 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w310w416w518w619w720w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xfc2493d3…6898
0x34b655…2a6f
6 touches
3 conflicts
0x988a4601…13d6
0x34b655…2a6f
5 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity