← previous blocknext block →recent activity
Analyzing
Block #104,977,152
22 transactions · 21 stateful · 2026-09-15 07:46:28 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,977,152 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w09w110w211w012w114w316w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cef1eff…9f14
0x34b655…2a6f
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcd37684c…86f9
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
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
6 conflicts on slot 0x2cef1eff78…339f14
Audit this contract →
← previous block·next block →recent activity