← previous blocknext block →recent activity
Analyzing
Block #104,877,533
16 transactions · 16 stateful · 2026-09-14 23:25:11 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,877,533 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w28w09w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
6 touches
3 conflicts
0xe5d33ef9…c031
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x253a6e6b…2206
0x99c7a7…8bf0
4 touches
1 conflict
0x55b8c286…4219
0x40c49f…2af0
4 touches
1 conflict
0x971f63ee…1f24
0x754704…b603
4 touches
1 conflict
0xb7f9a293…6bca
0x754704…b603
4 touches
1 conflict
0xde39c8f7…33f7
0x754704…b603
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
3 conflicts on slot 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity